Follow up issue to check enabling the no-deprecated rule for element-ng
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 22
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 118
Description
Closing as discussed in core team, Follow up issue to check enabling the rule for element-ng
Originally posted by @akashsonune in https://github.com/siemens/element/issues/1662#issuecomment-4731360822
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test. Start by locating element-ng's lint configuration and checking whether the no-deprecated rule can be enabled without existing violations; review the resulting diagnostics and project checks. Done means the rule is enabled for element-ng, or the blockers are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100