-
Notifications
You must be signed in to change notification settings - Fork 17
IBX-4929: Fixed PhpDoc in various places #226
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
Merged
Merged
Changes from 10 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
9002235
Fix @see usage
adriendupuis d8e26cc
Repository.php: Moved from @param to @phpstan-param
adriendupuis 832797b
RoleService.php: Fix @since usage
adriendupuis bee79a5
SearchService.php: Fix @since usage
adriendupuis 7a2dfb5
Repository.php: Fix phpdoc_separation
adriendupuis 0bd5d70
SearchResultAdapter.php: Fix @see vs @link usage
adriendupuis 8e79ab5
Specifications.php: Fix @see usage
adriendupuis e1c6ddc
Specifications.php: Fix @see usage
adriendupuis 48927b2
SearchResultAdapter.php: @see and @link can NOT be used in summary
adriendupuis 8721389
Update src/contracts/Repository/SearchService.php
adriendupuis 6261143
SearchResultAdapter.php: Rework phpDoc
adriendupuis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should rather be just
@since eZ Platform 1.0. Technically we can remove it, but I think it requires more discussion within PHP Team.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alongosz
@since eZ Platform 1.0causes the log entryTag "since" with body "@since eZ Platform 1.0" has error.https://docs.phpdoc.org/3.3/guide/references/phpdoc/tags/since.html defines in
@since [<version>] [<description>]the version number argument as optional, but, in fact, it is mandatory with phpDocumentor 3.3.1 which is looking for digit and dots only as first argument.It's only a log, no element skipped, the tag even renders properly. It could be kept as
@since eZ Platform 1.0with no or minimal annoyance.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm leaning towards dropping it entirely, at least for legacy Products. We can always infer that using
git log. But I think we're planning internal sync with you about the entire PHP API Reference, aiming to discuss that as well.