-
Notifications
You must be signed in to change notification settings - Fork 8
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
eFolder Rails 6.1 Rebase Alec k/appeals 46558 #1636
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Just a few minor changes needed. Let me know if you'd like to go over any of these together...
@@ -231,7 +230,7 @@ GEM | |||
bigdecimal | |||
rexml | |||
crass (1.0.6) | |||
d3-rails (5.9.2) | |||
d3-rails (7.8.5) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally, I would say we could omit this update to d3-rails
(though I realize it is being pulled in via the caseflow-commons
update).
However, it doesn't appear that d3
is being used at all in eFolder, so I guess it shouldn't hurt anything to update it 🤷
🎉 Thanks for addressing my concerns above! I'll make my final review/approval once department-of-veterans-affairs/caseflow-commons#225 gets merged and the associated ref is updated in |
📝 Note to self / other reviewers The following test failures are also present on other eFolder builds; They are not related to the changes in this PR:
|
ae6afa9
to
3e6eefa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎈
Removes `bourbon` and `neat` dependencies.
During assets precompile in a 'production' environment, we encountered the following error: Uglifier::Error: Unexpected token: name (compare1). To use ES6 syntax, harmony mode must be enabled with Uglifier.new(:harmony => true). Per the `uglifier` README: UglifyJS only works with ES5. If you need to compress ES6, `ruby-terser` is a better option. Looking at the Caseflow git history for comparison, it looks like the `uglifier` gem was removed in favor of using Webpack to perform JS compression via the `UglifyjsWebpackPlugin`. Later, the `UglifyjsWebpackPlugin` was removed when Webpack v4 incorporated the `TerserWebpackPlugin` out-of-the-box: https://github.com/department-of-veterans-affairs/caseflow-efolder/blob/9853eaeb98692099f1e62435de9a4dc08292fa53/client/yarn.lock#L6119 It appears that there may need to be some additional configuration added to the `webpack.config.js` file in order to leverage the Terser plugin: https://v4.webpack.js.org/plugins/terser-webpack-plugin/ However, the Caseflow `webpack.config.js` does not include the Terser configuration at this time, and so, in keeping parity with Caseflow, we will omit this configuration in eFolder as well and leave it as a future exercise should it be necessary to enact JS compression.
29cafbe
to
872b4a6
Compare
…okie_encryption` and `config.action_dispatch.use_cookies_with_metadata` While testing in PreProd, we discovered that, without these cookie config overrides, re-authentication was broken -- after logging out, a user could not log back in. Since the default settings are still optional going forward, we can restore these overrides and devise a solution to migrate cookies later. For more details, see Jira story APPEALS-54897: https://jira.devops.va.gov/browse/APPEALS-54897
Resolves APPEALS-43567
This is a revisit of the work done for APPEALS-28929 - updating eFolder to 6.1 PR
Description
🔴 Warning: Merge & deploy only after APPEALS-43566 has been merged to master. 🔴
Updates Rails to 6.1
Acceptance Criteria
Testing Plan
Regression testing via UAT
🔴 Warning: Merge & deploy only after APPEALS-43566 has been merged to master. 🔴