Replies: 1 comment
-
I still don't get why my source needs to state that it's going to be run under emulation. It's config, not code. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
The answer is probably "no," but I figured I might as well bring it up to see if others have run into this as well. So
useFirestoreEmulator
is the equivalent ofdb.useEmulator
in@exp
.The problem is that for React applications
useFirestoreEmulator
looks like React Hooks. The code itself is fine, but it causes a false positive with theeslint-plugin-react-hooks
. Because Hooks begin withuse*
and this is not being used within a React component it complains.I've disabled the warning, but just thought I'd see if there'd be any interest in renaming it to maybe
withFirestoreEmulator
? 😄Thanks!
Beta Was this translation helpful? Give feedback.
All reactions