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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC #0395 - Tracking for @ember-data packages #11

Open
kategengler opened this issue Feb 12, 2019 · 4 comments

Comments

4 participants
@kategengler
Copy link
Member

commented Feb 12, 2019

RFC #0395 - Tracking for @ember-data packages

Champion: @runspired


Ember Data Team:

  • convert to monorepo
    馃敀 @HeroicEric emberjs/data#5919
  • publish new packages
    馃敀 @runspired as part of 3.10 -beta
  • update blueprints to use new packages
    馃敀 @runspired emberjs/data#6045
  • mappings for use by codemods and lint rules
    馃敀 @dycriller https://github.com/ember-data/ember-data-rfc395-data
  • provide codemod for converting from DS. to new structure
    馃敀 @dcyriller
  • provide codemod for converting from ember-data/ to new structure
    馃敀 @dycriller
  • introduce a lint rule deprecating use of DS. and ember-data/ imports
    馃敀 @dycriller
  • provide mechanism to test "canary" builds
  • eliminate usage of DS. namespace in yuidoc comments in favor of correct package names/imports

Learning Team:

Ember CLI Team

N/A

@runspired

This comment has been minimized.

Copy link

commented May 13, 2019

I've introduced a label for tracking issues and PRs related to this effort in ember-data here: https://github.com/emberjs/data/labels/TRACK-packages

@runspired

This comment has been minimized.

Copy link

commented May 13, 2019

Note that we missed the 3.10 release target for this in part due to the continued need to validate/update documentation and documentation generation. We will need to make this a key focus for the 3.11 cycle to ensure we can release packages then.

cc @jenweber for some insight on how we can help on this.

@kategengler

This comment has been minimized.

Copy link
Member Author

commented May 13, 2019

@runspired If you can serialize the tracking here too, that'd be great. The checklist enables seeing progress of the RFC.

@jenweber

This comment has been minimized.

Copy link

commented May 13, 2019

@runspired I think maybe what we should do is pair the docs generation testing. It's helpful to have some people on the data team who are familiar with it, in order to help speed up future refactors too and protect against dropping things. Can you ask the team if anyone would like to pair it with me or maybe @sivakumar-kailasam, if he's available? We can get this locked down for 3.11. I don't expect any major issues.

If you want to give it a try solo, the linked issue has the instructions (emberjs/data#6016). I think they are fairly complete, though I have never done the API docs app viewing for ember data before, only ember.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can鈥檛 perform that action at this time.