Skip to content

Don't replace global config with pyproject.toml one, overlay pyproject.toml one over the global one #3391

@KOLANICH

Description

@KOLANICH

Is your feature request related to a problem? Please describe.

If a user wants to require a certain aspect in pyproject.toml, he can do it. If he doesn't do it, then it means he doesn't care. It should be up to the global config of the one running the tool. If a user wants to enforce the black-default value, he can define a field, but leave it as None and black should set the default value for that field.

Describe the solution you'd like

config = dict(globalConfig)
config.update(pyprojectConfig)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions