make serialization_context available in link

[f-mer]

Purpose

module MyEngine
  class Engine < Rails::Engine
    isolate_namespace MyEngine
  end
end

class MySerializer < ActiveModel::Serializer
  link :self do
    context.url_helpers.api_resource_url(object)
  end
end

module MyEngine
  class MyController < ApplicationController
    def index
      render json: @resources, url_helpers: my_engine
    end
  end
end

Makes it possible to build urls of engines with isolated namespace by passing the ActionDispatch::Routing::RoutesProxy (my_engine).

Changes

Pass serialization_context to link.

[mention-bot]

@f-mer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @domitian, @sigmike and @bf4 to be potential reviewers.

[bf4]

any reason you can't use the scope?

[bf4]

should probably mirror usage in pagination links?

• https://github.com/f-mer/active_model_serializers/blob/a6a8f53cadc1205b19f0ead41ab5c3f2d03bed10/lib/active_model_serializers/adapter/json_api/pagination_links.rb
• https://github.com/f-mer/active_model_serializers/blob/a6a8f53cadc1205b19f0ead41ab5c3f2d03bed10/lib/active_model_serializers/adapter/json_api.rb#L507

[f-mer]

Thanks for getting back at this! Yep that was the idea.
While exploring the problem it may be possible to just pass the view_context:

render json: @resources, scope: view_context, scope_name: :view_context

Links could be build like this:

link :self do
  view_context.api_resource_url(object)
end

and the current_user could also be accessed via view_context.current_user.
This would make the change obsolet. Have not tested this yet.

[bf4]

@f-mer how's it going? Have you seen #1981

[f-mer]

Closing this pull request because scope / view_context could be used.
Thank you heaps!