-
Notifications
You must be signed in to change notification settings - Fork 3
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
2024 Q1 Rails Upgrade #974
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…, we should add this to our Gemfile.
… so safe to remove the dependancy gem in our Gemfile.
…ient js libraries Fixes issues caused by updating versions of the ember-rails and ember-data-source gems by running the following: rails generate ember:install --tag=v1.6.1 --ember rails generate ember:install --tag=v0.14 --ember-data ...and committing the files the commands place in `vendor/`
…-5-fix-frontend fix: ember was broken, and some assets failed to load
…ken Rails 5.0 belongs_to.
…mview fails https://unep-wcmc.codebasehq.com/projects/species-rails-upgrade/tickets/139 If a user edits names in change_type so that either ADDITION or DELETION is missing, then this function will concatenate NULL while building SQL, leading to a confusing error message.
... so that it's clear when it's all done
https://unep-wcmc.codebasehq.com/projects/species-rails-upgrade/tickets/90 NB: https://github.com/aws/aws-sdk-ruby/blob/version-3/UPGRADING.md > Aws.eager_autoload! is deprecated as all autoload statements have been > replaced with require statements. Calling this method will now generate > a warning and have no other effect.
Upgrade: Ruby 3.0.6; Rails 6.1.7.6
…taint deprecation warning
This commit changes the format of matching_criteria so that the values of the hash are always strings, in order that we don't get errors on account of type mismatches, e.g. `{ "some_id": 123 } @> {"some_id": "123"}` is false. https://unep-wcmc.codebasehq.com/projects/species-rails-upgrade/tickets/102
Upgrade rails 6.1.7.6 to 6.1.7.7
…errors Fix for errors on some nomenclature changes
RSpec results for reference
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrades: