Fredrik Nicol

What about ([Regexr](http://regexr.com/3g6p8))? ```regex .([^:{]+)(:[^{]+)?{([^:]+):(".*?"|'.*?'|.*?)} ``` EDIT: Realized it wouldn't cover e.g. ```css .a:after{content:"hello } world" attr(title)} ``` So this may be an alternative ([Regexr](http://regexr.com/3g6pb)): ```regex .([^:{]+)(:[^{]+)?{([^:]+):(.*?)}(?=[\.]|$) ```

> There are a numerous properties that take keywords but are typed with their union of accepted string literals, but also include the string type in the union. Adding the...

I could give this a shot.

A workaround using `lint-staged` is to create a run-script that change to Git root directory before `git-exec-and-restage`: ```js // `.lintstagedrc` in subdir { "gitDir": "../", "linters": { "*.{ts,tsx}": ["precommit-prettier"] }...

You need this patch `react-native-modalize+2.1.1.patch` due to [this issue](https://github.com/software-mansion/react-native-gesture-handler/issues/139#issuecomment-790329701). ```patch diff --git a/node_modules/react-native-modalize/lib/index.js b/node_modules/react-native-modalize/lib/index.js index 5d5edac..d4c61c0 100644 --- a/node_modules/react-native-modalize/lib/index.js +++ b/node_modules/react-native-modalize/lib/index.js @@ -657,7 +657,7 @@ onOpen, onOpened, onClose, onClosed, onBackButtonPress,...

+1

Adding `string & {}` to all properties makes this an autocomplete tool only and basically ignore type checking. The goal is actually to avoid `string & {}`. But sometimes the...

Sorry for the long wait and thank you for your contribution 🙏 This however has been implemented now with the published types from `@mdn/browser-compat-data`.

> There's also [view-transition-class](https://developer.mozilla.org/en-US/docs/Web/CSS/view-transition-class) 🙏 Added in 3.2.0

Thanks for letting me know. Getting a bit overwhelmed with all the info here. Help would be very much appreciated.