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

Angle bracket blueprint #17685

Merged
merged 2 commits into from
Mar 2, 2019
Merged

Conversation

sukima
Copy link
Contributor

@sukima sukima commented Mar 1, 2019

This PR supersedes #17666 and attempts to address issue #17625

When generating the blueprints for a component the component-test blueprint will attempt to generate a test that uses Angle Bracket Syntax unless it sees that the component is nested in a path requiring the generated test to fallback and use Curly Bracket Syntax.

Prior to this change, the blueprints generated curly brace syntax for
the component-test.

This change will default to generating the angle bracket syntax unless
it finds the component being generated has any nesting (which is not
supported by angle bracket syntax) in which case it fallsback to the
curly bracket syntax.

Fixes emberjs#17625
Based on an original implementation by @ppcano
Prior to this change, the command `ember g component x-foo --path foo`
was originally producing angle bracket syntax but this seems incorrect
and should be the full nested invocation and curly bracket syntax.

This change fixes that oversight.

Issue found and discussed with @ppcano via Discord.
@rwjblue rwjblue merged commit 964a4fe into emberjs:master Mar 2, 2019
@rwjblue
Copy link
Member

rwjblue commented Mar 2, 2019

Thank you!

@sukima sukima deleted the angle-bracket-blueprint branch March 3, 2019 14:26
simonihmig added a commit to simonihmig/ember.js that referenced this pull request Mar 16, 2019
Removes incidental use of QUnit's `assert()` introduced in emberjs#17685.
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.

2 participants