-
Notifications
You must be signed in to change notification settings - Fork 101
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
[YAML] [Structure] [Suggestion] Use lists rather than maps #175
Comments
Not sure how that is logic to imply groupId and artifactId but no version. |
If anything I can image:
|
The implying was kinda just me over-DRYing. Your suggestion is basically what I was shooting for. I just tried to group the artifacts by common groupIds I will update the OP now EDIT |
Aren't these the same thing and both supported by YAML syntax? |
- {foo: bar, bleep: bloop}
- {foo2: bar, bleep2: bloop} is equivalent to - foo: bar
bleep: bloop
- foo2: bar
bleep2: bloop Both are a list of mappings. The curly braces are just a short-form for writing a map. The YAML parser should treat both the same. But by far my favorite way to write deps is using the dependencies:
- id: "org.springframework.boot:spring-boot-starter-web"
- id: "org.mapstruct:mapstruct:1.4.2.Final" |
The current structure
just doesn't look quite right. What I had imagined it as is something like this
The use of lists rather than maps actually makes it easier to read (although, that is subjective).
The text was updated successfully, but these errors were encountered: