Inherit views (V2)

[jhollinger]

Changes:

• V2 blueprints inherit views from parents (like Legacy/V1)
• view option to skip inheriting fields from the parent
• Freeze a blueprint/view's extensions, options and fields after it's first eval'd
• Disallow defining a :default view
• If a view is redefined, append to the existing definition instead of replacing it (like Legacy/V1)

Legacy/V1's "identifier" view can be emulated like this:

class ApplicationBlueprint < Blueprinter::V2::Base
  field :id

  # this view will not inherit any fields
  view :identifier, empty: true do
    field :id
  end
end

[siba2893]

This looks amazing! Waiting for this to get merged

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jhollinger]

Take another at the fields options (maybe inherit_fields). Use existing setters to clear options & extensions.

[jhollinger]

@lessthanjacob I've tentatively settled on an empty: true option to skip inheriting fields.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.