SchemaStore / SchemaStore/schemastore
Poetry v2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 2.3k
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 124
Description
Description of the JSON schema.
Since the release of Poetry v2, the schema of [tool.poetry] has been deprecated in favor of the standard [project] metadata definitions in the pyproject.toml file.
In a project that has been migrated to this new major, I get the following false positive errors (using the Even Better TOML VSCode extensions:
"name" is a required propertyEven Better TOML
"version" is a required propertyEven Better TOML
"description" is a required propertyEven Better TOML
"authors" is a required propertyEven Better TOML
I suppose the scheme needs updating? Thanks
Supporting information.
https://python-poetry.org/blog/announcing-poetry-2.0.0
Are you making a PR for this?
No, someone else must create the PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the schema for Poetry's [tool.poetry] and standard [project] metadata in pyproject.toml, then compare it with the Poetry 2.0 migration guidance. Reproduce the false positive required-property errors using the Even Better TOML VSCode extension. Done means migrated Poetry v2 projects no longer report obsolete required fields while the schema still validates applicable metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100