Skip to content
This repository was archived by the owner on Sep 16, 2021. It is now read-only.

generate annotations in yml format #603

Closed
wants to merge 1 commit into from
Closed

Conversation

dbu
Copy link
Member

@dbu dbu commented Nov 3, 2014

replaces #568

i went with yml rather than annotations. what would annotations do, service definitions by annotations?

@dantleech
Copy link
Member

I would prefer it to be xml to be honest, as that is the first example we show when showing examples in all formats.

@dbu
Copy link
Member Author

dbu commented Nov 3, 2014

the first .. configuration-block:: i see starts with yml first, so that is what is shown. but i have no strong opinion here, we can go with explicit xml format too. (this will make it visible to the users how they could achieve yml if they prefer that)

@dantleech
Copy link
Member

Oh yeah. You are right, guess I must be subconsciously clicking XML without noticing :P in that case yml is fine as a default for me.

@@ -427,7 +427,7 @@ and add some posts::
}
}

The
The
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like a very strange line...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed. just saw it cut the trailing blank, but it looks like a whole paragraph was lost during some editing here... would need to look at blame i guess or the history of this file to figure it out. can do tonight.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was already broken in the original commit: 6f21e4b - i tracked further back and did not find where the The appeared. just dropping it.

@wouterj
Copy link
Member

wouterj commented Nov 3, 2014

Annotations would use @Template, @Route and services in XML.

As the best practice is using that, I'm leaning a bit towards using it aswell. On the other hand, I'll do a walkthrough to be consistent with the best practices after Sf2.6 is released.

@dbu dbu force-pushed the generate-best-practice branch from 0a7ffb6 to 2bf785f Compare January 18, 2015 10:44
@dbu
Copy link
Member Author

dbu commented Jan 18, 2015

okay, updated

@dbu
Copy link
Member Author

dbu commented Jan 21, 2015

ping @wouterj

@wouterj
Copy link
Member

wouterj commented Jan 21, 2015

This should be merged into 1.1, I believe?

(we should create a plan about when to deprecate versions)

@dbu
Copy link
Member Author

dbu commented Jan 21, 2015

agreed. i can merge on cli if you want

@dbu
Copy link
Member Author

dbu commented Jan 21, 2015

if its all good, that is

@wouterj
Copy link
Member

wouterj commented Jan 21, 2015

Thanks David.

wouterj added a commit that referenced this pull request Jan 21, 2015
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
@wouterj wouterj closed this Jan 21, 2015
@wouterj wouterj deleted the generate-best-practice branch January 21, 2015 17:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants