MarketSquare / MarketSquare/robotframework-tidy
More configurable separators in NormalizeSeparators
Nobody has claimed this yet.
- Dominant language
- RobotFramework
- Stars
- 113
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Allow to configure how some separators behaves, for example FOR:
```
FOR ${var} ${var2} IN ZIP @{list1} @{list2}
END
```
uses 4 spaces by default for FOR arguments where it could use 2. Same goes for keyword arguments, tags etc. It could be possible to configure some separators to create more concise output.
Refer to RF coding style guide for inspiration what could be configurable.
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
Start by reading NormalizeSeparators and the referenced Robot Framework coding style guide to identify which separator rules should be configurable. Done means the formatter can configure separators for FOR arguments and the other named constructs, producing the requested concise output.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100