Skip to content

add a proc mechanism to Blacklight::Configuration#property to allow deferred resolution of some default values#2720

Closed
barmintor wants to merge 1 commit intomainfrom
configuration-property-procs
Closed

add a proc mechanism to Blacklight::Configuration#property to allow deferred resolution of some default values#2720
barmintor wants to merge 1 commit intomainfrom
configuration-property-procs

Conversation

@barmintor
Copy link
Copy Markdown
Contributor

…eferred resolution of some default values

- 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
- fixes #2705
@barmintor barmintor requested a review from cbeer May 12, 2022 18:51
@barmintor
Copy link
Copy Markdown
Contributor Author

I'm not enamored of this mechanism, but... it works. Without something like this, I was left using nil for the default and overriding accessors, which appears to be the 7.x approach we want to move away from.

@barmintor barmintor marked this pull request as draft May 13, 2022 14:55
@barmintor
Copy link
Copy Markdown
Contributor Author

Converting this to a draft as there may just need to be zeitwerk changes implemented in the plugins, see projectblacklight/blacklight_range_limit#185

@barmintor
Copy link
Copy Markdown
Contributor Author

Closed as was #2705

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

1 participant