-
-
Notifications
You must be signed in to change notification settings - Fork 79
breaking: drops Ember < 3.28, upgrades to Ember 4.12, supports Ember 5
#741
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
base: main
Are you sure you want to change the base?
Conversation
|
ping @nlfurniss 🙏 🙂 |
| options: AjaxOptions | ||
| ): FetchOptions { | ||
| const hash = assign( | ||
| const hash = Object.assign({}, |
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 think we may need to drop support for ember < 4 to do this as 3.28 still supports IE 11
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.
PR updated
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 that true 🤔 this just moves out of the concern of the addon and could be handled by a babel plugin or something
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.
essentially it would be bad if we dropped support for 3.28 for no reason
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.
ember-fetch does not work on Ember 5 without this change
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.
sorry I wasn't 100% clear 🙈 we should make this change, but we shouldn't stop testing in Ember 3.28
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 updated the PR.
I had to remove support for Ember < 3.28 because of ember-qunit but that's about it.
So this PR now supports Ember >= 3.28 (including Ember 5).
I've refactored the code so that neither the ember assign polyfill nor Object.assign() are used in production code. So IE is also still supported.
98e00f1 to
e95211a
Compare
8c13f95 to
7e6860b
Compare
Ember 4, drops Ember 3, supports Ember 5
68b337e to
a34cd17
Compare
Ember 4, drops Ember 3, supports Ember 5Ember 4, drops Ember 3, drops IE, supports Ember 5
e9e915a to
9bec330
Compare
Ember 4, drops Ember 3, drops IE, supports Ember 5Ember < 3.28, upgrades to Ember 4, supports Ember 5
Ember < 3.28, upgrades to Ember 4, supports Ember 5Ember < 3.28, upgrades to Ember 4.12, supports Ember 5
6b54de5 to
6012eeb
Compare
6012eeb to
8ea8d17
Compare
c0239d8 to
0c7dc29
Compare
dee80b2 to
5316d6d
Compare
5316d6d to
c6ebc58
Compare
|
All tests are passing except for 5 mocha tests failing during |
|
ping @xg-wang 🙏 ☝️ |
Breaking
drops
Ember < 3.28drops
Node < 16.14lru-cacheinstalled byember-sourceChore
upgrades to
Ember 4.12supports
Ember 5import { assign } from '@ember/polyfills'which no longer exists inEmber 5