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

[FR] Allow --tool to overwrite? OR option to disable all plugins loaded by entry-points? #174

Open
abravalheri opened this issue May 17, 2024 · 0 comments

Comments

@abravalheri
Copy link
Owner

abravalheri commented May 17, 2024

I run into a situation that I wanted to test local schemas changes in setuptools and see if they work first before cutting new releases to validate-pyproject.

So my strategy was to have local .spec.json files and load them with --tool ...=file://....
However I run into a problem:

[ERROR] SchemaWithDuplicatedId: All schemas used in the validator MUST define a unique toplevel `"$id"`

This happens because the plugin is loaded from an entry-point and from tool.

So I thought about to alternatives not mutually exclusive:

  1. Allow --tool to always overwrite whatever plugin is loaded from entry-points (I believe this is done in Allow overwrite when schemas refer to the same tool #175).
  2. Add an option to the CLI to disable all plugins loaded from entry-points1

Footnotes

  1. This might also be useful for improving reproducibility. But it becomes more complicated to handle if we also allow "extra" (non-tool, "side-car") plugins to be loaded from entry-points, in the sense that we would have a bunch of open questions...

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