Loris Sigrist

I would love to see an exception for `role="list"` and `role="listitem"` Many CSS resets add `list-style: none`, including the one used by tailwind, so this workaround is quite often necessary.

+1 on this suggestion This would come in handy when doing i18n work and you need to set the `lang` attribute on the `` element

I just had another thought about this. Instead of magically giving the developer the "type" of the form, consider the opposite. Passing an interface to a form that then gets...

This would also be quite valuable for i18n use-cases, since the language of the error-message usually needs to be determined the moment parsing happens instead of upfront when the module...

We can infer which values would pass the match function using the following generic: ```typescript const fruits = ['apple', 'banana', 'cherry'] as const type Fruit = typeof fruits[number] export const...

In the example it would be directly in the root folder. A `[[lang]]` parameter is not needed with this approach. Any incoming request to `/de/about` gets rewritten to `/about`. If...

The language _would_ be part of the URL. That's the difference between a rewrite and a redirect. A rewrite doesn't change the URL, it just changes which route get's resolved....

I'll be splitting this PR into two PRs, one for each hook. Once the new PRs are submitted I will close this one

I had suspected that the `resolveDestination` hook might be _too_ magic, so I won't open a separate PR for it. It's functionality can also largely be implemented using a Preprocessor,...

Just to make it clearer how this would enable i18n routing