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
formatter should start a new line for each annotation #17938
Comments
Added Area-Formatter, Triaged labels. |
Set owner to @pq. |
This comment was originally written by caitpot...@gmail.com I have a patch for this at https://codereview.chromium.org/226063005 (which might be trying to fix it in the wrong place, the dart tree is very confusing) |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Added AssumedStale label. |
This issue has been moved to dart-lang/dart_style#343. |
This issue was originally filed by @zoechi
What steps will reproduce the problem?
1.
formatter generates:
@NgComponent(selector: 'alert', publishAs: 't', applyAuthorStyles: true,
templateUrl: 'packages/angular_ui/alert/alert.html')@NgComponent(selector:
'[alert]', publishAs: 't', applyAuthorStyles: true, templateUrl:
'packages/angular_ui/alert/alert.html')
class Alert {
@NgOneWay('type')
String type;
2.
3.
What is the expected output? What do you see instead?
@NgComponent(selector: 'alert', publishAs: 't', applyAuthorStyles: true,
templateUrl: 'packages/angular_ui/alert/alert.html')
@NgComponent(selector:
'[alert]', publishAs: 't', applyAuthorStyles: true, templateUrl:
'packages/angular_ui/alert/alert.html')
class Alert {
or even better
@NgComponent(
selector: 'alert',
publishAs: 't',
applyAuthorStyles: true,
templateUrl: 'packages/angular_ui/alert/alert.html'
)
@NgComponent(
selector: '[alert]',
publishAs: 't',
applyAuthorStyles: true,
templateUrl: 'packages/angular_ui/alert/alert.html'
)
class Alert {
What version of the product are you using? On what operating system?
Dart VM version: 1.3.0-dev.7.5 (Fri Mar 28 04:58:12 2014) on "linux_x64"
Please provide any additional information below.
The text was updated successfully, but these errors were encountered: