-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Deprecate @link and add relations to @see #2
Comments
I like this concept and would support it. Are there any constraints on what |
My suggestion would be to provide recommendations, as is done with the rel attribute for a link, and allow people to come up with their own. I would also suggest to maintain the recommendations outside of the standard in a living document so that those may change without affecting the actual PSR |
I'm all for this. Have something in the meta docs that explains some recommended types, but do not actually list anything (or reference them at all) in the main doc. |
removing the \Baz that does not exist in the path to finding Quux
I have altered the text to deprecate |
…atement Made the mission statement less wordy
Fix the EventInterface::stopPropagation() method
This proposal intends to add a relation type, or role, to the
@see
tag while keeping the tag backwards compatible.Syntax proposal:
Example:
The relation type is considered to be an optional addition and may be omitted.
I also propose to create a separate list, or recommendations, for type names; this will help standardize and provide default meaning (comparable to http://www.iana.org/assignments/link-relations/link-relations.xhtml for the rel attribute of a link)
The text was updated successfully, but these errors were encountered: