Best-effort fix of typos

[joellabes]

If there's a known key (say, description) which is not present in a model but there's a similarly-spelled invalid key present (say, desciption), it's probably safe to update the spelling instead of moving it to a config.

"similarly-spelled" is left as an exercise to the implementor, waves hands wildly Levenshtein distance or whatever

Before:

models: 
  - name: my_model 
    desciption: "This is a very useful model which does things" #this is misspelled! 

  - name: my_second_model
    desciption: "idk what this is doing here" # this is misspelled 
    description: "This is the true descriptor of the model"

After:

models: 
  - name: my_model 
    description: "This is a very useful model which does things" # this has been fixed, because there wasn't a competing description key

  - name: my_second_model
    description: "This is the true descriptor of the model"
    config: 
      meta: 
        desciption: "idk what this is doing here" #this was moved to config.meta, because there was already a competing correctly-spelled description key. 

[b-per]

There is already some logic to mention when a field is a potential typo. Right now though it moves it under config.meta as-is and just adds a comment for people to review.

The example you wrote above is the current behavior of the tool, no? If so, what would you expect to happen?

We could add auto-fixing potential typos as a behavior but then it means that we would change the behavior of the project in comparison to the state it was before running the tool. Until now, all the changes are "transparent" from a config/behavior point of view.

[joellabes]

The example you wrote above is the current behavior of the tool, no? If so, what would you expect to happen?

I don't think so - the first model also had a typo, but that typo was auto-fixed instead of being moved. Also it was not a config property. (Edited to make that more clear)