Skip to content
This repository has been archived by the owner on Feb 5, 2023. It is now read-only.

Detect and report potential errors in formatting blocks #83

Open
robertjank opened this issue Nov 20, 2021 · 0 comments
Open

Detect and report potential errors in formatting blocks #83

robertjank opened this issue Nov 20, 2021 · 0 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@robertjank
Copy link
Collaborator

Sometimes formatting blocks get messed up. Examples are:

  • 'text':class="block3control"} Opening brace { missing.
  • 'text'{: class = ""} Empty value string between double quotes ".
  • (text): target = "_ blank"} Opening { missing.
  • 'text'{;class="block3looks"} Semicolon ; used instead of colon:.
  • 'text':{class="block3looks"} Opening brace { and colon : swapped.
  • 'text'{:clsss="block3looks"} Keyword class misspelled as clsss.

NTTT may not be able to fix these kinds of errors (because that may require knowledge about the context), but should help the user to locate these errors, such that the user can fix these errors manually.

NTTT should be extended such that it can detect these kind of errors and report them to the user of NTTT.
False positives (NTTT reports a potential error, which turns out not to be an error) should be as small as possible. (This requirement should be quantified, because now it is not verifiable).

@robertjank robertjank added enhancement New feature or request question Further information is requested labels Nov 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant