-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Documentation about Yaml, mention it as discouraged to use? #7321
Comments
@doctrine/team-documentation can we do something about this one? |
This should get a highlighted box at the beginning of the page mentioning its deprecation and removal. I guess this part of the ORM documentation can be removed for the right ORM version. |
I would be +1 for removing it on the latest minor version docs. Basically, because it is now deprecated, why show it at all? Older versions of the docs will still exist for existing users to reference. We can cleanup the new version right now. |
It's already known to be deprecated and 2.6 is the current documentation. If a developer takes a look at the documentation, and doesn't see a deprecation, chances are that everything is going to be created in Yaml. This is a waste of time for the developer because it's already known to disappear with 3.0. Not letting the developer know this as soon as possible, will thus result in extra work while it was not necessary. |
Looks good to me! |
#7374 has been merged into 2.6. |
Summary
The documentation page about Yaml does not mention anything about it being removed/unsupported in the future. I think it's a good idea to mention on here that it's discouraged to use Yaml as configuration.
Whenever I see people suggest to not use Yaml because it's going to be removed as core supported configuration, the response is usually "oh I did not know that".
The text was updated successfully, but these errors were encountered: