-
Notifications
You must be signed in to change notification settings - Fork 156
Conversation
This is a small issue, almost nagging When you generate the bundle without interaction, the services and routing files in the bundle are in xml format. Strange because the YAML version is always first in the row. Confusing. I don't think there is an option to specify YAML format, is it? So I went for generating the bundle with interaction
@dantleech do you have an opinion here. i guess the change by simon makes sense if there is no parameter to make the command generate yml files without interaction. |
You can specify the format with I would personally prefer that we add that option to the example, and explain that they can change that option as they want (for example by adding a I fear that if its interactive then people will be "creative" and things won't work. |
oh, good. then lets add --format=yml (that was the idea, i think?) what |
@DoneBySimon did you try the |
ping |
ping @DoneBySimon |
The team that created the best practices used |
continued in #603 |
see #603 |
This PR was submitted for the master branch but it was merged into the 1.1 branch instead (closes #603). Discussion ---------- generate annotations in yml format replaces #568 i went with yml rather than annotations. what would annotations do, service definitions by annotations? Commits ------- 9cf0231 generate annotations in yml format. fix #568
This is a small issue, almost nagging
When you generate the bundle without interaction, the services and routing files in the bundle are in xml format.
Strange because the YAML version is always first in the row. Confusing.
I don't think there is an option to specify YAML format, is it?
So I went for generating the bundle with interaction