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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepares Ember CLI for new version of ember-welcome-page #6378

Merged
merged 1 commit into from
Oct 27, 2016
Merged

Conversation

locks
Copy link
Contributor

@locks locks commented Oct 23, 2016

  • Update ember-welcome-page dependency
  • Re-introduce application.hbs template to include the new
    welcome-page component
  • Release new ember-welcome-page version

@nathanhammond
Copy link
Contributor

nathanhammond commented Oct 23, 2016

@ember-cli/core Thoughts on having Ember CLI run the default blueprint of any addon present after ember new or ember addon? This would avoid us having to hardcode what amount to blueprint-level changes into our app/addon blueprints.

I'm hesitant to enshrine what feel like blueprint related tasks into our blueprints. If y'all feel like that's a good feature I'll build it today (so that welcome-page may adopt it).

@Turbo87
Copy link
Member

Turbo87 commented Oct 23, 2016

@nathanhammond 💯 👍 (see #6269)

@kellyselden
Copy link
Member

Sounds good to me. ember init will probably want this feature too.

@nathanhammond
Copy link
Contributor

I'm less sure about ember init as it's intended to be run in projects that are already set up.

@locks
Copy link
Contributor Author

locks commented Oct 23, 2016

I'm less sure about ember init as it's intended to be run in projects that are already set up.

We should have this as a different thing 🤔

@kellyselden
Copy link
Member

I'm less sure about ember init as it's intended to be run in projects that are already set up.

What about the scenario, you're doing an ember-cli upgrade via ember init. The default blueprint for package.json updated ember-cli-eslint from ^1.0.0 to ^2.0.0. There was a big default blueprint change in ember-cli-eslint that you need to run.

Isn't that the same problem as with new and addon?

@nathanhammond
Copy link
Contributor

@kellyselden You make a good point. But unfortunately that implies that default blueprints must be idempotent/safe to rerun which is not something that we require at this time since they're only ever invoked once. This is a larger problem than I was thinking and I no longer want to block this PR on that effort.

@kellyselden
Copy link
Member

Good point as well, I wasn't thinking of the blowing away of previous custom changes to blueprint. Carry on, no changes to ember init.

@nathanhammond
Copy link
Contributor

Hokay, so, @locks, this is not blocked by CLI people's opinions. Just tests passing once the new version is released.

@locks locks force-pushed the welcome-page branch 3 times, most recently from 2e51b01 to 0b7721f Compare October 26, 2016 00:39
- Update ember-welcome-page dependency
-  Re-introduce application.hbs template to include the new
welcome-page component
@nathanhammond
Copy link
Contributor

@homu r+

@homu
Copy link
Contributor

homu commented Oct 27, 2016

📌 Commit 58b7431 has been approved by nathanhammond

@nathanhammond
Copy link
Contributor

@locks Thank you for your tireless efforts on this!

homu added a commit that referenced this pull request Oct 27, 2016
Prepares Ember CLI for new version of ember-welcome-page

- Update ember-welcome-page dependency
-  Re-introduce application.hbs template to include the new
welcome-page component

- [x] Release new `ember-welcome-page` version
@homu
Copy link
Contributor

homu commented Oct 27, 2016

⌛ Testing commit 58b7431 with merge cf97908...

@homu
Copy link
Contributor

homu commented Oct 27, 2016

☀️ Test successful - status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants