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.

Sign up for GitHub

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

Jump to bottom

Support relative paths to blueprint packages without publishing packages for those blueprints? #1051

Open
NullVoxPopuli opened this issue Jun 3, 2020 · 0 comments
Open

Support relative paths to blueprint packages without publishing packages for those blueprints? #1051

NullVoxPopuli opened this issue Jun 3, 2020 · 0 comments

Comments

@NullVoxPopuli
Copy link

NullVoxPopuli commented Jun 3, 2020 •
edited

While developing a new series of blueprints, I haven't published anything yet, so... I don't think there is a way to test ember-cli-update for real (via actual invocation in the terminal).

My scenario:

  • create default ember addon
  • apply a number of tiny unpublished blueprint "diffs" that ember-cli-update can apply based on some CLI-based user interaction
  • 🎉 modified addon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NullVoxPopuli