Perhaps we should document this issue in the FAQ? Using pre-commit with Black is pretty common (and it's not always instantly clear it passes all of the files to the hook directly bypassing any file discovery the hook may implement). I'd suggest pre-commit's exclude configurations first, and then black's force-exclude.

_Originally posted by @ichard26 in psf/black#3013

I've faced a problem that importing dowhy.plotter lead to incorrect visual settings for all future rendered plots.

It would be great to avoid overriding default matplotlib settings:
https://github.com/microsoft/dowhy/blob/master/dowhy/plotter.py#L7-L13

A possible solution is to encapsulate these settings into dowhy.plotter functions instead of overriding global variables.

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

If

Which @angular/* package(s) are the source of the bug?

router

Is this a regression?

No

Description

The Documentation suggests that you can supply a function to runGuardsAndResolvers . The link will take you to the documentation where it gives the type.

So I supplied the following and saw that not only was my route guard s

Describe the problem

the low level documentation (https://svelte.dev/docs) is not really easy to use ( and incomplete in some cases)
I think if the runtime function contain JSDOC it will help a lot and give the developers an easier way to discover api documentation

additionally it is possible to replace the https://svelte.dev/docs with the generated docs ( with some thing like https://ty