Would it be possible to let folks pass their own slugify function to generate slugs for markdown headings? Some usecases for this are

• backward compatibility (if I'm migrating from some other framework)
• customization of slugs (one off custom transformations)
• handling special usecases for non-latin languages (like Urdu)

Possible alternative

If it is too much, [@sindresorhus/sl

Why?

In some case we only get the linter errors for projects only in CI, it takes a lot of time for the whole cycle.

How?

We can add lint-staged for the existing husky setup on a recommit hook.

We should handle the lint-staged for all the packages in the app, including docs folder.

see https://github.com/ssciwr/clang-format-wheel and https://github.com/pre-commit/mirrors-clang-format

need to update contributing doc if it requires installing additional dependencies.

We have a lot of is_prime (or similar) functions: https://github.com/TheAlgorithms/Python/search?p=4&q=is_prime, https://github.com/TheAlgorithms/Python/search?q=isPrime, data_structures/hashing/number_theory/prime_numbers, etc. Shall we use one common function for that exactly identical

We should set up a GitHub action to test changes made in every PR via the existing Playwright setup. Would complement nicely with the Vercel deployment.

I see the Guid has been added, can you add the test "type.IsPrimitive || type.isEnum || ..." in the IsKnownImmutableType, because using a constant enum parameter always raise the SetParameter for a component.

https://github.com/dotnet/aspnetcore/blob/7b22a279ec975335bbb0a7cbadef2e45ee15aa9c/src/Components/Components/src/ChangeDetection.cs#L39

Feature request

We currently have 2 monocular depth estimation models in the library, namely DPT and GLPN.

It would be great to have a pipeline for this task, with the following API:

from transformers import pipeline

pipe = pipeline("depth-estimation")
pipe("ca