ApplicationBlueprinter pattern

[toobulkeh]

Is there any reason not to use the Application pattern with Blueprinter?

application_blueprint.rb:

class ApplicationBlueprint < Blueprinter::Base
  identifier :id
end

user_blueprint.rb:

class UserBlueprint < ApplicationBlueprint
  fields :name
end

[philipqnguyen]

Definitely! There is no reason not to use the ApplicationBlueprint pattern. It is already a pattern that Procore is using internally as well and I highly recommend using that pattern in your projects.

[toobulkeh]

Apparently extending a blueprint with an identifier removes it from the returned value. Is that expected?

IE, I had to add this line back to all of our blueprints:

identifier :id

[philipqnguyen]

I did a short test of your example locally and I can confirm you're correct and that it does not work. Will have to look into it further.

[Systho]

The problem is the view collection is a class instance variable, thus it's not the same in the parent class and in the subclass.

I've personally fixed the problem with this snippet in my BaseBlueprint

  class BaseBlueprint < Blueprinter::Base

    def self.inherited(sub_class)
      sub_class.identifier :id
    end

end

[philipqnguyen]

@Systho you're right, class instance variable is the problem. I think you have the right solution.

[philipqnguyen]

resolved by #105