-
Notifications
You must be signed in to change notification settings - Fork 4
Javadoc issues #134
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
Open
mlopezFC
wants to merge
2
commits into
master
Choose a base branch
from
javadoc-issues
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Javadoc issues #134
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Oops, something went wrong.
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.
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.
Documentation is accurate but there's a method duplication issue.
The documentation for
setDrawerRightAlignment
is clear and accurately describes the method's purpose. However, there appears to be a duplicate methodsetDrawerBelowHeader
that still exists with different behavior.Consider removing the
setDrawerBelowHeader
method if it's being replaced bysetDrawerRightAlignment
, or clarify the relationship between these methods if both behaviors are intended to coexist.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.
Comment must be addressed (https://github.com/FlowingCode/TechnicalDocs/blob/master/addons/pr-process.md)
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.
@javier-godoy,
Thanks for pointing this out. From the script output, we can see that the method setDrawerBelowHeader is indeed used in test classes (DemoSettings and ApplayoutDemoView), so removing it completely would require aligning those references or clarifying the difference in intended behavior between “drawer below header” and “drawer right alignment.” If the plan is to replace setDrawerBelowHeader entirely with setDrawerRightAlignment, we should deprecate or remove setDrawerBelowHeader and update the test code accordingly. Alternatively, if both methods are still needed for different scenarios, we should clarify in the Javadoc why these two methods coexist and what each one does distinctly.
Let me know how you prefer to proceed:
• Remove setDrawerBelowHeader and references from the test classes, or
• Retain and clarify both methods’ purposes if they serve separate use cases.
I’m happy to help with either approach!
🔗 Analysis chain
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 10583