Justinas Delinda

I think the idea is that we need to rename the rule to be more consistent with other rules `noRestrictedImports`, `noRestrictedGlobals` and now ~~`noBannedTypes`~~ `noRestrictedTypes`, ts-eslint also renamed theirs. Adding...

@ematipico Sorry been bit distracted, will fix up this PR this week.

> I think that we should follow the lead of TypeScript ESLint that decided to [split no-banned-types into several rules](https://typescript-eslint.io/rules/ban-types/). For now, we could keep noBannedTypes to ban types like...

After doing quick search for [enum graphql](https://github.com/search?q=enum+language%3Agraphql&type=code) there are a lot of different casing examples, so this rule is likely too restrictive. I think this functionality would be better served...

What device are you using? Can you provide video for playlist creation not working? Can you show pictures of UI widget getting out of bounds? Can you say more specifically...

I think could be handled by https://biomejs.dev/linter/rules/use-naming-convention/#typescript-enum-names ? --- If you are planning on working issue yourself, you can open straight up and someone will assign you, but you do...

I think originally the idea was that multiple languages can have the same rule. Like for example json language has `useSortedKeys`, the same rule could be implemented for javascript as...

It does. Though bit annoying that another config file is needed, (I use biome) but it works. So I guess this would be a feature request to improve formatting if...

Currently we use loaders (0.7) in SPA app, it would very annoying if suddenly all those page loaders became possibly undefined inside pages, one of the reasons I chose this...

@posva am I correct in thinking that after https://github.com/posva/unplugin-vue-router/pull/506 types will have undefined value even on non lazy non server loaders? That would be major DX regression, from our own...