Update to Ruby 3.0 with updated dependencies #106
Conversation
* Updated gems with latest version as of 2022-01-03
* .ruby-version * .tool-versions * .rubocop.yml * Gemfile
* Gemfile.lock * test_app/Gemfile.lock
* config/webpacker.yml * babel.config.js * package.json * yarn.lock
* The setup script produces an updated db schema definition based on current migrations. Committing updated schema for consistency.
|
Thank you for the pull request and these updates! |
Codecov Report
@@ Coverage Diff @@
## main #106 +/- ##
=======================================
Coverage 96.35% 96.35%
=======================================
Files 24 24
Lines 548 548
=======================================
Hits 528 528
Misses 20 20 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
@radamson Seems that there are some linting issues that need to be resolved. I started going through them but the fixes will require various i18n-related changes across the project. Should those be committed as part of this pull request or would it make more sense to push those in another pull request? |
|
Commiting those changes to this PR would be great if you are willing to take a stab at it! I can also look into fixing the linting issues and then open a PR into this one if you don't beat me too it. Thank you again for the PR! |
Updating this project to use Ruby 3.0.5. No major Rails update was made.
The following changes were also made in conjunction:
rails,sqlite3,puma,sass-rails,webpacker,turbolinks,jbuilder,bootsnap,fhir_models,rubocop-minitest,rubocop-rake,web-console,listen,rack-mini-profiler,capybara.Dockerfileto use Ruby3.0.5.Gemfile.lockfiles (using bundler2.4.2)18.12.1config/webpacker.yml,babel.config.js,package.jsonandyarn.lockusing webpacker.bin/webpackrequired settingexport NODE_OPTIONS=--openssl-legacy-providerto avoid errors.db/schema.rbto the version generated bybin/setup.README.mdto reflect the Ruby version update.This solves #105