Add schema: Hugo

[EmilyGraceSeville7cf]

• non-object global properties
• build property
• caches property
• cascade property
• frontmatter property
• imaging property
• markup property
• mediaTypes property
• menus property
• minify property
• module property
• outputFormats property
• permalinks property
• related property
• security property
• sitemap property
• taxonomies property
• prettify schema:
  • standardize all descriptions
  • add title property to all objects to make errors more descriptive

[EmilyGraceSeville7cf]

@GerryFerdinandus, what to do with Duplicate fileMatch found => config.json? Is it a critical error? Some tools can have similar named configs but as I know JSON schema could be chosen when such conflict occurs (in VS Code for instance).

[GerryFerdinandus]

@EmilySeville7cfg
AFAIK IDE, like visual studio and intelliJ, don't tell the user that they may have used the wrong schema.

Visual studio code tells me something is wrong. example using deploy.yml in github action does not work.
I still can't figure out how to disable the wrong conflicting schema.

remove the "fileMatch": []" to avoid conflict

[EmilyGraceSeville7cf]

@GerryFerdinandus, please merge this PR. After it I'll move this schema to HUGO repo. 😄

[EmilyGraceSeville7cf]

remove the "fileMatch": []" to avoid conflict

My solution: add config.json to fileMatchConflict in src/schema-validation.json. We need to describe this file better (in .md).

[GerryFerdinandus]

@EmilySeville7cfg
I can't merge additional name conflict/hijack. Maybe @madskristensen is willing to accept this merge.

[madskristensen]

config.json is way too generic of a name. It will have way too many false file matches.

[EmilyGraceSeville7cf]

As I understand schema link to config.json for Hugo site must be set-up in .vscode/settings.json before using. @madskristensen, you can merge this PR. 🚀

[madskristensen]

Thanks