Wasif Hossain

@ameerh I think you also dont need `@import "font-awesome";` can you try again after removing the line? thanks

@ameerh so you are sure that you removed all font-awesome `import/require` variations as well as related gems still getting the error: `File to import not found or unreadable: font-awesome` ?...

@rromanchuk turning it off will also keep the app missing the awesome feature (**recyclable cache key**) introduced since Rails 5.2. Also **Rails 6 will turn it ON by default**. AMS...

Given that you are on `rails 5.2` as well as cache_versioning is turned on, you can use `cache_key` to leverage the `recyclable cache key` concept explained in https://blog.heroku.com/cache-invalidation-rails-5-2-dalli-store. This link...

as it looks, your expected structure does NOT match any of the available adapters (attributes/json/json-api). so you have to DIY, by defining the association fields at the top-level serializer like...

Hi @LeKristapino that was unfortunate. but upgrading to the latest HEAD of the `0-10-stable` branch should resolve the issue. ``` gem 'active_model_serializers', :git => 'https://github.com/rails-api/active_model_serializers.git', :branch => '0-10-stable' ``` This...

@LeKristapino I think I am wrong here. that PR does not fix the case yet! I see it now :( Actually that was kind of like a side-effect while implementing...

@LeKristapino can you share some code to reproduce the fail case. Specifically how `SomeCustomSerializer` looks like when you pass `{first_key: "some string", second_key: "another string" }` in `render json:` call

@LeKristapino as bf4 mentioned, can you try your issue on other AMS versions later than 0.10.5 but earlier than 0.10.10 and let us know how you found it?

@LeKristapino thanks for the insight. btw AMS should have already covered the case, like: **formatting the attribute name or the value as needed by the api client**, and that is...