Max Isaev comments

Results 11 comments of


                                            Max Isaev

Status of useMutation not shared across usages/components with custom hook (like useQuery does)

If I understood the reason correctly, the following worked for me: ```tsx // workaround for https://github.com/TanStack/query/issues/2304 // instead of useIsMutating const [isMutating, setIsMutating] = useState(false); useEffect(() => { return queryClient.getMutationCache().subscribe(({...

[bug] Failed to compile.

You need to add .babelrc to compile class props during build ``` { "plugins": ["@babel/plugin-proposal-class-properties"] } ``` ____________ I can’t build and check anything locally because you have complete chaos...

[bug] Failed to compile.

Dealt with versions and build (lock file is absolutely required) Please see the new PR - https://github.com/SortableJS/react-sortablejs/pull/247

class $7fe8e3ea572bda7a$export$11bbed9ee0012c13 extends $8zHUo$react.Component {

Should be fixed in #244 and #247

Types node fix

@dbbring @dustinsmith1024 @garrypolley @doug-martin Is there someone alive?)

Types node fix

Any update? Or the project is not maintained anymore?

[bug] Failed to compile.

Any update? Or the project is not maintained anymore? Looks like we're should migrate to beautiful-dnd)

React 18 compatability

Any update? Or the project is not maintained anymore?

evaluateOptions property gets deleted from .yaml file when it is edited through the web ui

Hi @mldangelo, thanks for the quick response — I'm looking forward to the new version! As related, `defaultTest` is showing the same behavior — could you take a look at...

evaluateOptions property gets deleted from .yaml file when it is edited through the web ui

Thank you! I really appreciate your quick response! I'm not sure about the sorting — this one seems quite logical to me: - description - env - evaluateOptions - extensions...