You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will be longer-term, and we'll need to ensure the Samvera components we use are compatible. If we want to do a Bootstrap upgrade, there will be lots of JavaScript configuration decisions to make. Now that Avalon is on Rails 7, is it time to make this move? Things might continue working as they are, but rethinking the way we do JS bundling might be needed.
There are deprecation warnings that pop currently when running Avalon; these will need to be resolved as part of this process. We'll need to either change things in Avalon or our dependencies so we're not using deprecated methods.
Done Looks Like
Upgrade to Blacklight 8.4
Refactor Blacklight customizations to the new way of encapsulating components within the Ruby code
Try out/investigate deep pagination indicator and pagination strategies in Blacklight 8 to reduce Solr load
The text was updated successfully, but these errors were encountered:
Note: Blacklight 8 does not have a release for Rails 7.2 yet so if we complete the Ruby/Rails upgrade first we will need to wait for support to be added before starting this upgrade. Conversely, we could complete this upgrade first if Ruby/Rails is too sticky an upgrade.
Description
Blacklight 8.4 has been released: https://github.com/projectblacklight/blacklight/wiki/Upgrading-to-Blacklight-8. Should Avalon upgrade Blacklight versions as well, and what would this entail?
This will be longer-term, and we'll need to ensure the Samvera components we use are compatible. If we want to do a Bootstrap upgrade, there will be lots of JavaScript configuration decisions to make. Now that Avalon is on Rails 7, is it time to make this move? Things might continue working as they are, but rethinking the way we do JS bundling might be needed.
There are deprecation warnings that pop currently when running Avalon; these will need to be resolved as part of this process. We'll need to either change things in Avalon or our dependencies so we're not using deprecated methods.
Done Looks Like
The text was updated successfully, but these errors were encountered: