You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, a big thank you for creating this package. It's really helpful.
I'd like to know if it would be possible for you to instead of console.warn("Replacing an existing Haven instance. Are you sure this behaviour is intended?");if you could simply return the existing instance.
But now I'm getting a console error because getInstance() has this console.error("No Haven instance found. Make sure to create a Haven instance before attempting to access it.")
Thank you
The text was updated successfully, but these errors were encountered:
What exactly is your use case here, i.e. how are you getting to the point that you have multiple conflicting Haven.create() calls? The error message is there because usually that shouldn't be happening.
However if I don't check if an instance already exists, then it will create new ones.
I was wondering it this could be something that the library could handle since we aren't supposed to create multiple instances, instead of simply warn the user to actually return the existing instance.
Hi,
First of all, a big thank you for creating this package. It's really helpful.
I'd like to know if it would be possible for you to instead of
console.warn("Replacing an existing Haven instance. Are you sure this behaviour is intended?");
if you could simply return the existing instance.create would be like this
If we have already an instance then there's no point in creating a new one right?
In my code I'm doing
But now I'm getting a console error because
getInstance()
has thisconsole.error("No Haven instance found. Make sure to create a Haven instance before attempting to access it.")
Thank you
The text was updated successfully, but these errors were encountered: