Inheritance principle: Include enumeration indices in source #2
Conversation
There was a problem hiding this comment.
Just to give a try if it would work to disable "one" ordering check for the block following https://github.com/remarkjs/remark-lint#ignore-warnings
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
|
Works; but I'll defer to maintainers the conversation around whether or not this is something you want to permit / permit in this fashion / permit everywhere. (Personally: I see no point in enumerating unless you intend on referring to a specific entry; if that's not the case, they should be bullet points instead. I'd almost prefer that appropriate enumeration in code be enforced, since if the entries / order changes, the rest of the source needs to be checked for cross-references) |
|
Would this also lead to a rendering of list items as |
…ids-standard#1299) * Pet recon method tweaks (#2) * add conditionals for ReconMethod Metadata * add min and max values to scatter fraction * add conditional for ReconFilterSize * Apply suggestions from code review * Update pet.yaml * use intersects for 'none' check, switch to recommended * Apply suggestions from code review Co-authored-by: Chris Markiewicz <effigies@gmail.com> Co-authored-by: Chris Markiewicz <effigies@gmail.com> Co-authored-by: Stefan Appelhoff <stefan.appelhoff@mailbox.org>
Testing to see whether or not including enumeration indices in the source code as proposed here does or does not result in a CI complaint about formatting.