Skip to content
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

Document and test status quo for AnnotatedElementUtils [SPR-11514] #16139

Closed
spring-issuemaster opened this issue Mar 4, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Mar 4, 2014

Sam Brannen opened SPR-11514 and commented

Status Quo

The public methods and internal algorithms in AnnotatedElementUtils are currently poorly documented or not documented at all. Furthermore, there are practically no regression tests in place to verify the current behavior.

Deliverables

  1. Document "get vs. find" semantics in the class-level Javadoc as well as for each public method.
  2. Document all public methods in AnnotatedElementUtils.
  3. Document internal search algorithms within AnnotatedElementUtils and rename methods, variables, etc. as necessary to make the intent clear.
  4. Test all public methods in AnnotatedElementUtils.

Affects: 4.0 GA

Issue Links:

  • #17533 Document meta-annotation support in AnnotationUtils
  • #16136 Introduce a comprehensive programming model for meta-annotation support
@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 6, 2015

Sam Brannen commented

AnnotatedElementUtils is now fully documented and fully tested!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.