-
Notifications
You must be signed in to change notification settings - Fork 6
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
GN-4800: Bump appuniversum to v3 #645
Conversation
Converted to Draft as P.S. Ready for review again |
* Bump * Remove deprecations
@dkozickis I think dependency lint is just because there's a new peer-dep for AU >3. I think that there's more to this upgrade though than this, unfortunately the problems will only come up by either testing every template in the app or searching for deprecated uses of components, since we don't have TS and glint to lint our templates. When doing this in the plugins, I looked at the release notes of AU and checked the usage of the components. For example v2.13.0 includes this deprecation of |
|
@dkozickis Ah, sorry, when I looked at the PR it was just the dependency change, none of the code changes, I guess I caught it when not all the commits were in. |
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.
LGTM, just one comment. Happy for it to be merged after that or if there's a good reason not to do it.
package.json
Outdated
@@ -29,7 +29,7 @@ | |||
"release": "release-it" | |||
}, | |||
"devDependencies": { | |||
"@appuniversum/ember-appuniversum": "~2.15.0", | |||
"@appuniversum/ember-appuniversum": "~3.4.1", |
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.
Personally I think we can go for ^3.4.1
as AU versions follow semver pretty well.
@@ -111,7 +111,9 @@ | |||
}, | |||
"overrides": { | |||
"@appuniversum/ember-appuniversum": { | |||
"tracked-toolbox": "^2.0.0" | |||
"tracked-toolbox": "^2.0.0", | |||
"ember-concurrency": "^2.3.7", |
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.
Is there a reason to override this rather than upgrading? I tested this PR with ^3.1.0
and it seems to work.
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.
I've preferred to override to 2.3.7
because all other dependencies have it, below is the output of ember dependency-lint
, I will crate tech tasks to update ember-concurrency
everywhere else 🤔
ember-concurrency
Allowed: (any single version)
Found: 3.1.1, 2.3.7
frontend-gelinkt-notuleren
├── [email protected]
├─┬ @appuniversum/ember-appuniversum
│ └── [email protected]
├─┬ @lblod/ember-mock-login
│ └── [email protected]
├─┬ @lblod/ember-rdfa-editor-lblod-plugins
│ └── [email protected]
└─┬ ember-power-select
└── [email protected]
Overview
GN-4800: Bump
@appuniversum/ember-appuniversum
to3.4.1
Bump
@appuniversum/ember-appuniversum
to3.4.1
AuTextarea
andAuInput
components.appuniversum
SCSS is imported in the app.AuDatePicker
localisation.Bump
@lblod/ember-rdfa-editor-lblod-plugins
to17.0.0
Bump
@lblod/ember-environment-banner
to0.5.0
connected issues and PRs:
Setup
npm i
How to test/reproduce
ember s --proxy https://dev.gelinkt-notuleren.lblod.info
Checks PR readiness