Skip to content
This repository has been archived by the owner on May 12, 2020. It is now read-only.

We should log warnings when a validated class has no reachable methods or RAVE-specific ones are not reachable #19

Open
ZacSweers opened this issue Apr 9, 2017 · 0 comments
Open

We should log warnings when a validated class has no reachable methods or RAVE-specific ones are not reachable #19

ZacSweers opened this issue Apr 9, 2017 · 0 comments
Labels
enhancement
Milestone
RAVE 3

Comments

@ZacSweers
Copy link
Contributor

ZacSweers commented Apr 9, 2017 •
edited

Since we don't support multiple validator factories per compilation unit, we should log a warning if a class denotes itself as validated but has no reachable methods (e.g. if a validated class has all package/protected methods but the validator factory is in a different package)

We should also log warnings when RAVE-specific annotated methods (e.g. @MustBeTrue are also not reachable)
@ZacSweers ZacSweers changed the title We should log warnings We should log warnings when a validated class has no reachable methods Apr 9, 2017
@ZacSweers ZacSweers changed the title We should log warnings when a validated class has no reachable methods We should log warnings when a validated class has no reachable methods or RAVE-specific ones are not reachabel Apr 9, 2017
@ZacSweers ZacSweers changed the title We should log warnings when a validated class has no reachable methods or RAVE-specific ones are not reachabel We should log warnings when a validated class has no reachable methods or RAVE-specific ones are not reachable Apr 9, 2017
@naturalwarren naturalwarren added this to the RAVE 3 milestone May 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
RAVE 3
Development

No branches or pull requests
2 participants
@naturalwarren @ZacSweers