Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally think that using an
if
here, might make this more readable:What do you think?
Another possibility would be to prepend the empty string within
blueprints/model/index.js
. We are already doing that for theneeds
statement, so I think this would be fine forattrs
too...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pangratz Thanks for the feedback!
The problem I run into with the
if
condition is that if I do pass in attrsember g model foo --attrs name, title
I get empty lines surrounding them:
The ternary doesn't have that issue. I tried the suggestion found here: #4306 (comment) using
-%>
but received anUnexpected token
error no matter where I used it (both for the closingif
and<%= attrs -%>
).I saw that ternary used here https://github.com/emberjs/data/blob/master/blueprints/model-test/qunit-files/tests/unit/__path__/__test__.js#L5 so went that route. But I agree that it isn't that readable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, ok. Thanks for the heads up @sbatson5. Let's leave it then the way it is, we can always change this later on.