trent
trent
> I think we should keep the state 'readonly', but I think we could have a 'cancel/abort' option for `useAsyncState`. I don't think that correct. State with this `useAsyncState` is...
> > State with this useAsyncState is intentionally not read only. > > I am not sure about that. Let's save for instance that I have a `useAsyncState` that returns...
> For this usecase you should consider https://vueuse.org/core/useCloned I'm really having trouble understanding the push back. You've offered two suggestions now without giving any reasoning to help us understand why...
@43081j @OrbisK so regardless of how this original issue I outlined is solved, are you suggesting that `useAsyncState` needs to be "fixed" like this? ```diff export interface UseAsyncStateReturnBase { -...
[mysticatea/eslint-plugin-node](https://github.com/mysticatea/eslint-plugin-node) is another [incomplete](https://github.com/mysticatea/eslint-plugin-node/issues/258) implementation using it's [`node/file-extension-in-import`](https://github.com/mysticatea/eslint-plugin-node/blob/8ef07af5711b74199745a619c6f522e1e32acfaf/docs/rules/file-extension-in-import.md) rule.
@edison1105 Where is the carrot syntax in mentioned in the docs?
Found it! The caret is actually a shorthand for the `.attr` modifier. https://vuejs.org/api/built-in-directives.html#v-bind
> Found it! The caret is actually a shorthand for the `.attr` modifier. https://vuejs.org/api/built-in-directives.html#v-bind Actually, I don't think that's accurate. It seems that the `^` prefix doesn't treat the value...
For the sake of not reinventing the wheel, I just wanted to share my Vue directive for consideration when implementing this feature. [@roydukkey/custom-highlight](https://github.com/roydukkey/custom-highlight)