-
Notifications
You must be signed in to change notification settings - Fork 65
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
Restore the Blacklight logo for generated apps #3198
base: main
Are you sure you want to change the base?
Conversation
If we force at least Blacklight 7.38 and use the ESM module, Blacklight handles this.
The selection prompt may be causing problems on CI?
Currently BL8 has corresponding frontend packages for all versions.
Address propshaft related CI & test failures
Require version of OSD rails that supports turbo
The Blacklight default logo-image is currently using the sprockets image_url helper. This overrides logo-image using the propshaft url helper.
@taylor-steve is it possible to fix this in Blacklight instead? |
@jcoyne I haven't been able to think of a good method yet. Two separate SASS entry points could work? E.g., |
@taylor-steve I don't think that blacklight really wants to continue supporting Sprockets primarily, so I think we could accept this change upstream. What about doing |
@jcoyne yes, that definitely works with propshaft and I'd expect it to work with sprockets. I don't love that it would separate the logo from the release versions. Although maybe that's better for a logo anyway, defaulting to using the most current branding? I'll think on it a bit more, but you're probably right that it's the best solution. |
64c0c4b
to
fbea85a
Compare
ffea72a
to
7e12176
Compare
The Blacklight default logo-image is currently using the sprockets image_url helper. This overrides logo-image using the propshaft url helper.
This is the same convention Geoblacklight is using.