Inherit views (V2)

[jhollinger]

Changes:

• V2 blueprints inherit views from parents (like Legacy/V1)
• view options to skip inheriting certain attributes from the parent (i.e. fields, options, extensions)
• 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)
  • If they want to replace it, they can do so using view's new field/options/extension options

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

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

  # without `fields: false`, this view would inherit fields from the top-level of child Blueprints
  view :identifier, fields: false do
    field :id
  end
end

[siba2893]

This looks amazing! Waiting for this to get merged