Skip to content
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

feature/APPEALS-46558 - Rails 6.1 upgrade (uat) #1678

Merged

Conversation

jcroteau
Copy link
Contributor

@jcroteau jcroteau commented Sep 6, 2024

Contains changes from the following PR(s):

AKeyframe and others added 30 commits August 13, 2024 12:35
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.
…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
@jcroteau jcroteau changed the title feature/APPEALS-46558 - Rails 6.1 upgrade feature/APPEALS-46558 - Rails 6.1 upgrade (uat) Sep 6, 2024
@jcroteau jcroteau marked this pull request as ready for review September 6, 2024 16:07
@sbashamoni sbashamoni merged commit a5c3f06 into uat/Rails6.1-Upgrade Sep 6, 2024
3 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants