forcedotcom / forcedotcom/code-analyzer
[Feedback] How to Ignore Warnings in Flow Engine?
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 5
Description
### Feedback
We would like to enforce Flow Engine in our projects, but we see that some flows would require massive refactoring to remove all warnings. Is there any way to Ignore issues in Flows, similar to PMD or ESLint?
### Context
_No response_
### Suggestions
_No response_
### Additional Information
_No response_
### Are you interested in contributing to this project?
Yes, I'd like to contribute.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating Flow Engine warning handling and any existing suppression or configuration support, then compare the available behavior with the PMD or ESLint examples in the request; done requires a clearly defined, tested way to ignore selected Flow issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100