adopted-ember-addons / ember-paper

The Ember approach to Material Design.
https://ember-paper.netlify.app/
MIT License
888 stars 333 forks source link

feat: ember@4 support #1256

Closed matthewhartstonge closed 1 month ago

matthewhartstonge commented 1 month ago

@mansona it builds... Haven't got to the point of running codemods/testing it yet as I just needed our apps to compile on ember@5 before circling back to upgrading/fixing ember-paper

mansona commented 1 month ago

ooo nice one! 🎉 it looks like we're both thinking the same thing at the moment 😂

matthewhartstonge commented 1 month ago

oop, looks like I need to merge in upstream..

matthewhartstonge commented 1 month ago

Do you have contrib access to ember-css-transistions? There is a bug in the repo that needs to be fixed:

https://github.com/miguelcobain/ember-css-transitions/compare/master...matthewhartstonge:ember-css-transitions:master?expand=1

mansona commented 1 month ago

I don't have access to ember-css-transitions no, but it looks like it's active enough so I wouldn't worry about opening up a PR there.

Why are you asking about utils though? It looks like the deployed version of the package is inlining the utils imports in the dist: https://unpkg.com/browse/ember-css-transitions@4.4.0/dist/modifiers/css-transition.js#L44

matthewhartstonge commented 1 month ago

omg... you're kidding...

I couldn't see a mention to this change in the changelog, and theres an issue from last year that didn't clarify or point to where the utils had moved to: https://github.com/miguelcobain/ember-css-transitions/issues/120

Righto, all of these will be an easy change then!! one momento..

matthewhartstonge commented 1 month ago

Cool, so the tests look like they are failing due to scope (probably non-explicit this e.t.c).

I'll look at patching that tomorrow. :)

not ok 54 Chrome 129.0 - [42 ms] - Integration | Component | paper-dialog: click outside >should close dialog if clickOutsideToClose

stack: > Error: Attempted to resolve a value in a strict mode template, but that value was not in scope: dialogOpen

...

ok 308 Chrome 129.0 - [0 ms] - Unit | Validator | minlength: falsy values ok 309 Chrome 129.0 - [0 ms] - Unit | Validator | required: strings ok 310 Chrome 129.0 - [0 ms] - Unit | Validator | required: falsy values ok 311 Chrome 129.0 - [0 ms] - ember-qunit: Ember.onerror validation: Ember.onerror is functioning properly

1..311 tests 311 pass 30 skip 4 todo 0 fail 277

mansona commented 1 month ago

So if we get a small pr of yours merged then you won't need me to approve the tests any more.

Maybe extract the ember-css-transition upgrade on its own