URL host name is not generated properly in self link with serializer

[peco8]

I sometime use the serializer to render the reply from some API request like below.
In controller

    result = Hoge.find(1)
    resource = Object.const_get('HogeResource')
    serializer = JSONAPI::ResourceSerializer.new('HogeResource')
    body = serializer.serialize_to_hash(resource.new(result, nil))
    render json: body, status: 20

and the result is
http://localhost:3000/hoges/1

{
  "data": {
    "id": "1",
    "type": "hoges",
    "links": {
      "self": "/hoges/1"
    },
    "attributes": {

self should have the hostname like http://localhost:3000/amc/hoges/1

Any idea how to fix this?

[senid231]

to have hostname like http://localhost:3000/amc/hoges/1
you need to name your resource like Amc::HogeResource
and have json_api_resources :hoges in amc namespace

[peco8]

@senid231

Thanks for the response.
Yes, I added the name space but it's out of luck.

Anybody having the same issue?

[bobfirestone]

I just had to deal with a similar problem. In production the rails app serving up the api runs in a directory off of the domain. Not exactly the same problem but close.

// Development Response
{
  "data": [
    {
      "id": "AK",
      "type": "states",
      "links": {
        "self": "http://local.example.com:3000/v1/states/AK"
      },
      "attributes": {
      }
    },

// Production Response
{
  "data": [
    {
      "id": "AK",
      "type": "states",
      "links": {
        "self": "http://production.example.com/rails-app-name/v1/states/AK"
      },
      "attributes": {
      }
    },

To get this to work I overrode the base_url method in my application controller

class ApplicationController
  include JSONAPI::ActsAsResourceController
  private
  def base_url
    @base_url ||= if Rails.env.production?
      "#{super}/#{Rails.application.class.parent_name.underscore.dasherize}"
    else
      super
    end
  end
end

The call to super is calling the original base_url method from JSONAPI::ActsAsResourceController

[senid231]

Take a look at #980
It doesn't related to your issue but it has proposal of bug report template
Can you reproduce this issue using this template as example? This will help to understand whether it's a bug in library or just a mistake in its usage

[tobias-bischoff]

Unless this issue is with namespaced routes, see PR #1282 for a possible fix.