google / google/closure-compiler
Consider suspicious code check for declaring a protected method/property in a constructor/interface marked as @final
Open
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 1.2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 6
Description
This issue was imported from Closure Compiler's previous home at http://closure-compiler.googlecode.com
The original discussion is archived at:
http://blickly.github.io/closure-compiler-issues/#1127
Contributor guide
Research direction
Start by reading the archived discussion for issue 1127 linked in the issue body, since no source file, test, or entry point is identified here. A complete change would define and implement the suspicious-code check for protected methods or properties declared in a constructor or interface marked @final, with tests demonstrating the intended diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100