MarketSquare / MarketSquare/robotframework-robocop
Ship with multiple default rulesets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 269
- Forks
- 58
- Avg merge
- 4h 55m
- Merged PRs (30d)
- 45
Description
During lint rule severity discussions, we often talk about different kind of users. For example: A rule should maybe be `error` for an intermediate user bug `warn` for a beginner.
What do you think about shipping with multiple predefined rulesets? For example:
- Default
- Strict
- Loose
Alternatively, maybe a better way to grab a ruleset from a pypi package. This would, for example, allow me to publish `robocop-ruleset-super-duper-strict`. This is a similar idea to Eslint. Example config: https://github.com/google/eslint-config-google
Note: This is only about configuring lint and format rules. This does not include new rules or new formatters.
Background: In Slack we were discussing the potential need for highly opinionated docs/tools/configs. This is a way that we can achieve highly opinionated Robocop config.
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 names no files, tests, or entry points. Start by mapping how Robocop currently configures lint and format rules, then clarify whether predefined rulesets, PyPI-provided rulesets, or both are required; done should include an agreed configuration design and defined behavior for selecting each ruleset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100