Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future work: Add more types of rules #29

Open
SankBad opened this issue Mar 24, 2021 · 0 comments
Open

Future work: Add more types of rules #29

SankBad opened this issue Mar 24, 2021 · 0 comments

Comments

@SankBad
Copy link
Contributor

SankBad commented Mar 24, 2021

Currently, we are detecting spelling errors, data type errors, and missing entry errors by generating rules. In the future, we wanted to add more types of errors. Some of the types of errors we can include are as follows.

  1. Ordering rules: In configuration files, certain keyword (Let's say A) are always expected before certain another keyword (Let's say B). we wanted to find these explicit rules to detect ordering errors. In the above example, we entry of keyword A before keyword B.
  2. Correlation rules: These rules detect integer correlations: one entry’s value should have a certain correlation with another entry’s value. For instance, in MySQL, the value of key_buffer should be larger than max_allowed_packet
  3. Subnet rules: An entry is substring of another entry
  4. Filepath rules: Concatenation of a file path entry with a partial file path entry forms a full file path. For example:
    [A<FilePath>]+[B<FileName>] => [<FilePath>]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant