-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
chore: update v4-main infra and tooling to match main branch #9598
base: v4-main
Are you sure you want to change the base?
Conversation
…ion available versions
* Sync tests/main/tests/unit/record-arrays/record-array-test.js * Sync tests/main/tests/unit/record-arrays/adapter-populated-record-array-test.js * Get through most of unit/model
* Finish the models folder * Add legacy-compat tests * custom class model
update integration/records
* update tests/integration/references * fix easier to fix integration/relationships tests * update tests/integration/{serializers,store} * fix tests in integration (no subdir) * finish off unit tests (adapters, custom-class-support) * update more integration tests * all the tests migrated
Any movement on this? This bug seems to be blocking us from getting to LTS of ember-data 4 so we can be prepared to move to 5 |
@lfloyd117 what issue? |
@runspired |
@lfloyd117 not familiar with a discussion with anyone on that specific ticket: that said, the idea of 4.13 is that it contains all fixes and additions from V5 (while attempting to preserve deprecated things present in V4). I notice that particular fix never got backported (probably no one ever asked for it to be, would have been an easy one to), but yes it will be fixed in 4.13 too. |
@runspired I can ask them to check on this thread later (they are on a different timezone and not on currently). |
No description provided.