Skip to content

Consolidate legacy extensions - #604

Merged
jhollinger merged 5 commits into
release-2.0from
jh/release-2.0-merge-legacy-extensions
Sep 9, 2026
Merged

Consolidate legacy extensions#604
jhollinger merged 5 commits into
release-2.0from
jh/release-2.0-merge-legacy-extensions

Conversation

@jhollinger

@jhollinger jhollinger commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Merges most V2 "legacy extensions" into a single LegacyOptions. Two remain separate:

  • LegacyDynamicOptions (more expensive and new, so not widely used)
  • LegacyTransformer (it takes transformers as arguments)
class ApplicationBlueprint < Blueprinter::V2::Base
  # Legacy if, unless, default_if, name, extractor, and view-on-render options
  add Blueprinter::Extensions::LegacyOptions.new
end

class OtherBlueprint < ApplicationBlueprint
  # Legacy dynamic options
  add Blueprinter::Extensions::LegacyDynamicOptions.new

  # Legacy transformers
  add Blueprinter::Extensions::LegacyTransformer.new(MyTransformer)
end

Also adds a Performance page to the Building V2 Extensions section.

Drops test runs for Ruby 3.1 because it suddenly started throwing errors.

@jhollinger
jhollinger changed the base branch from main to release-2.0 September 4, 2026 14:07
@jhollinger
jhollinger force-pushed the jh/release-2.0-merge-legacy-extensions branch 4 times, most recently from cb5adf7 to 6fe9580 Compare September 4, 2026 14:45
@jhollinger
jhollinger marked this pull request as ready for review September 4, 2026 15:17
@jhollinger
jhollinger requested review from a team and ritikesh as code owners September 4, 2026 15:17
@jhollinger
jhollinger marked this pull request as draft September 4, 2026 15:25
@jhollinger
jhollinger force-pushed the jh/release-2.0-merge-legacy-extensions branch from 6fe9580 to a3f4f28 Compare September 4, 2026 15:36
@jhollinger
jhollinger marked this pull request as ready for review September 4, 2026 15:40
Signed-off-by: Jordan Hollinger <jordan.hollinger@procore.com>
Signed-off-by: Jordan Hollinger <jordan.hollinger@procore.com>
@jhollinger
jhollinger force-pushed the jh/release-2.0-merge-legacy-extensions branch 4 times, most recently from 78cb7a2 to c6ad3d6 Compare September 8, 2026 17:56
Signed-off-by: Jordan Hollinger <jordan.hollinger@procore.com>
…n when using expensive hooks (Claude)

Signed-off-by: Jordan Hollinger <jordan.hollinger@procore.com>
Signed-off-by: Jordan Hollinger <jordan.hollinger@procore.com>
@jhollinger
jhollinger force-pushed the jh/release-2.0-merge-legacy-extensions branch from c6ad3d6 to 316580d Compare September 8, 2026 19:26
@jhollinger

Copy link
Copy Markdown
Contributor Author

Merging bc this is a pretty clear win.

@jhollinger
jhollinger merged commit cae9581 into release-2.0 Sep 9, 2026
4 checks passed
@jhollinger
jhollinger deleted the jh/release-2.0-merge-legacy-extensions branch September 9, 2026 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant