Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defer resolving Blacklight::Configuration default properties so we can use auto-loaded classes #2826

Merged
merged 1 commit into from
Oct 6, 2022

Conversation

cbeer
Copy link
Member

@cbeer cbeer commented Oct 6, 2022

if property default values are not defined under lib, they may not be available until application is loaded, causing issues for downstream apps running generators.

This shouldn't be necessary, but it's difficult for plugins (and e.g. arclight which uses blacklight + some plugins) to convince zeitwerk to get the load order right.

Fixes #2705

(also see discussion from #2720)

@cbeer cbeer marked this pull request as draft October 6, 2022 16:28
@cbeer cbeer force-pushed the 2705-prop-default-proc branch 2 times, most recently from fbfb783 to ed08ba5 Compare October 6, 2022 17:03
@cbeer cbeer changed the title add a proc mechanism to Blacklight::Configuration#property to allow deferred resolution of some default values. Defer resolving Blacklight::Configuration default properties so we can use auto-loaded classes Oct 6, 2022
@cbeer cbeer marked this pull request as ready for review October 6, 2022 17:38
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.

Blacklight::DocumentFactory class is not loaded when Blacklight::Configuration property definitions are set
2 participants