Skip to content

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

Open
@abravalheri

Description

@abravalheri

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...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions