active-model-serializers

问题 I'm using active_model_serializer 0.10.0.rc5 and grape gem for the api. I've a post endpoint like this : class V1::Endpoints::Posts < Grape::API resource :posts do desc 'Returns a list of posts.' # serializing array get '', each_serializer: V1::Serializers::PostSerializer do @posts = Post.all present @posts end end end My serializer looks something like this : class V1::Serializers::PostSerializer < ActiveModel::Serializer attributes :id, :name, :slug end Now when I try to access the post

问题 I'm using active_model_serializer 0.10.0.rc5 and grape gem for the api. I've a post endpoint like this : class V1::Endpoints::Posts < Grape::API resource :posts do desc 'Returns a list of posts.' # serializing array get '', each_serializer: V1::Serializers::PostSerializer do @posts = Post.all present @posts end end end My serializer looks something like this : class V1::Serializers::PostSerializer < ActiveModel::Serializer attributes :id, :name, :slug end Now when I try to access the post

问题 I'm using active_model_serializer 0.10.0.rc5 and grape gem for the api. I've a post endpoint like this : class V1::Endpoints::Posts < Grape::API resource :posts do desc 'Returns a list of posts.' # serializing array get '', each_serializer: V1::Serializers::PostSerializer do @posts = Post.all present @posts end end end My serializer looks something like this : class V1::Serializers::PostSerializer < ActiveModel::Serializer attributes :id, :name, :slug end Now when I try to access the post

来源： https://stackoverflow.com/questions/52341102/difference-between-django-core-serializers-and-django-rest-framework-serializers

来源： https://stackoverflow.com/questions/52341102/difference-between-django-core-serializers-and-django-rest-framework-serializers

问题 The combination of multiple user models (User, Admin, and Master) with devise_token_auth does not successfully set the Response Headers (uid, token, etc.) upon login with non "User" models (Admin and Master); however, User model works. The cause looks to be the default serialization_scope (:current_user) in active_model_serializers/lib/action_controller/serialization.rb:18. Is there a way to set the serialization_scope, or do I need to override the controllers? Environment: Rails 4.2.6 AMS 10

问题 I have a model object that is not descended from ActiveRecord::Base and is not stored in the database. I created a serializer for it (with the same name + "Serializer"), and in my controller I'm calling render json: object_instance . The result is an exception from deep inside of render . I implemented an as_json method that instantiates the serializer and calls it, but the result is then a missing method in the object, read_attribute_for_serialization . I want my object to act like an

问题 I have a Client model and a method in my controller that should return the nearest clients. I'm using ActiveModel::Serializers but it's not working. class ClientSerializer < ActiveModel::Serializer attributes :id, :name, :path, :url def url client_url(object) end def path client_path(object) end end controller: def nearby_from_category @closest_clients = Client.from_category(params[:category]). activated.locateable.all_with_translation(@lang). by_distance(origin: remote_ip).limit(2) render

问题 I have the following models: class Appeal < ActiveRecord::Base belongs_to :applicant, :autosave => true belongs_to :appealer, :autosave => true end class Appealer < ActiveRecord::Base has_many :appeals, :autosave => true end class Applicant < ActiveRecord::Base has_many :appeals end What I want is for every appealer to hold a reference to the applicant of his last appeal so I modified Appealer model to: class Appealer < ActiveRecord::Base has_many :appeals, :autosave => true def last

问题 Unfortunately, ActiveModel::Serializers does not currently support validation errors, though they're scheduled for 1.0. Until then, I've got to hack a solution of my own. The big problem? I have no idea what format Ember Data's ActiveModelAdapter expects these errors to be in. I tried simply passing in the errors property, but Ember Data didn't pick up on it: class MySerializer < ActiveModel::Serializer attributes :errors end So what should I pass in instead? 回答1: I use this method to render