Skip to content

[Console] Add documentation for QuestionHelper#3752

Merged
weaverryan merged 1 commit intosymfony:masterfrom
romainneutron:question-helper
Apr 12, 2014
Merged

[Console] Add documentation for QuestionHelper#3752
weaverryan merged 1 commit intosymfony:masterfrom
romainneutron:question-helper

Conversation

@romainneutron
Copy link
Copy Markdown
Contributor

Q A
Doc fix? no
New docs? yes (symfony/symfony#10606)
Applies to 2.5+

This is the documentation for the new Question Helper

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[...] instead, which is more [...]

@wouterj
Copy link
Copy Markdown
Member

wouterj commented Apr 3, 2014

Thank you for writing this! I've put some comments and although they are not caused by you (since you somewhat copied the original article), I would appreciate it if you can fix them.

You also need to add this new document in the correct place in /components/console/helpers/index.rst and /components/console/helpers/map.rst.inc

@romainneutron
Copy link
Copy Markdown
Contributor Author

Sure !

it was indeed easier for me to port the dialog helper to question helper (as a matter of writing a brand new page).

@romainneutron
Copy link
Copy Markdown
Contributor Author

PR updated, comments addressed

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

maybe [...] is deprecated as of Symfony 2.5 [...], what do you think?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We used "has been deprecated in Symfony 2.5" in another PR today

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In #3461 we use deprecated as of as the short form. So, for consisteny I would use is deprecated as of as the long form.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

let me know which consistency I should use :)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

the question here is whether we look at the state of the feature (the helper is deprecated) or at the action of marking it as deprecated (The developers have deprecated this feature in 2.5 which gives as the feature has been deprecated in 2.5).

I would vote in favor of is deprecated by looking at the current state of the feature

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I like any of the following

is deprecated as of Symfony 2.5

was deprecated in Symfony 2.5

The second sounds a bit more natural, only because of the "as of" in the first sounds "ok" to me, but I don't know if that's so easy to understand for non-native speakers (but I have no idea!). I guess this is also consistent with the "was introduced" we're using for new features. It makes it sound like the deprecation of addition of features happened at a point in time, which makes sense to me.

Another fun editorial conversation :) - I think they're all "correct", so now it's just a matter of taste.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants