question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Restructure Checkers page in the documentation

See original GitHub issue

The Checkers page currently contains the main groups and inside these groups the rules are grouped by the checker classes. Due to this behavior the rules are not always ordered by their IDs. Example: the Spacing group starts with rule W1006.

The current order inside Spaces: InconsistentUseOfTabsAndSpacesChecker: W1006 InvalidSpacingChecker: W1001, W1002 MissingTrailingBlankLineChecker: W1003, W1004, W1005

It is obvious that we should put InconsistentUseOfTabsAndSpacesChecker class at the end since it has the W1006.

But what about the following scenario: we add a new rule to InvalidSpacingChecker with W1007 (since we don’t want to change the other rules’ IDs due to incompatibility issues), how should we order the classes? The only possible solution I can see in this scenario is that we somehow restructure the Checkers page.

Example:

  • The page still should have the main groups: Comments, Tags, etc.
  • Inside the groups we can have the rules ordered by the IDs (no need to group/separate by the checker classes).
  • And we can mention that which checker class contains the given rule (like we mention what parameters does it have).

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
szabolcstothcommented, Nov 16, 2020

Yes, this solves the original ordering issue inside the checkers, thanks for the fix! Later on we can have a brainstorming session about how to improve the page further. 👍

1reaction
bhirszcommented, Nov 13, 2020

I refactored our checker docs a bit, you can view test version here: https://robocop.readthedocs.io/en/refactor_docs/checkers.html Based on https://github.com/MarketSquare/robotframework-robocop/compare/master...refactor_docs Rules are directly under group instead of checker class and are ordered based on rule ID

What do you think & want we can improve further? @szabolcstoth @mnojek

Read more comments on GitHub >

github_iconTop Results From Across the Web

Staticcheck 2019.1 release notes
At the core of the 2019.1 release lies the grand restructuring of all of the Staticcheck tools. All of the individual checkers, ...
Read more >
Why do you need a text checker for government proofreading ...
Spelling and grammar checkers to polish government documents · Proofreading — correcting basic errors (spelling, grammar, punctuation, consistency) · Copy editing ...
Read more >
Documentation :: Corteza Docs
Follow the KISS principle! Keep things structured; Use admonition; Use images…​ sparingly; Use syntax checkers (and semantics checkers); User Roles; DevOps; End ...
Read more >
Restructure - OpenROAD documentation - Read the Docs
Restructure is an interface to ABC for local resynthesis. The package allows logic restructuring that targets area or timing. It extracts a cloud...
Read more >
International Traffic in Arms Regulations: Consolidation and ...
This rule restructures part 120 of the ITAR to better organize the definitions previously found in that part and other locations throughout ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found