`WETZEL_WARNING: title not defined` - is this required for every definition?
See original GitHub issueIn http://json-schema.org/draft-07/schema# and co., it seems that the title
key isn’t required for creating a json schema, but I get title not defined
as an error for wetzel trying to parse my schema…
Any help would be great! The files in question are at https://github.com/comp500/packwiz-spec/blob/master/schemas
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Part 2 - Definitions of Words and Terms | Acquisition.GOV
Contracting means purchasing, renting, leasing, or otherwise obtaining supplies or services from nonfederal sources. Contracting includes description (but not ...
Read more >Title Definition & Meaning - Merriam-Webster
noun ; 1 · b. : a similar distinguishing name of a musical composition or a work of art ; 4 · b....
Read more >Python nameerror name is not defined Solution - Career Karma
A NameError is raised when you try to use a variable or a function name that is not valid. In Python, code runs...
Read more >In Need of Definition: How to Select Terms to Define in your ...
The rule of thumb is to include and define terms that are important to your study or are used frequently throughout the dissertation...
Read more >NameError: name 'self' is not defined - python - Stack Overflow
Default argument values are evaluated at function define-time, but self is an argument only available at function call time.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve ended up using https://github.com/grafana/json-schema-markdown as an alternative, but all the best to you and your project!
I’m fairly sure this is happening because you don’t have a top-level title. For example in pack.json, you could add a title on line 3:
Otherwise the title must be inferred from the filename, which might end in *.json or in *.schema.json or might be something else entirely.
I’d prefer not to guess the title from the filename, because these titles end up in important places in the TOC and as anchor link names. So I think titles should be added at the tops of the schema files.