-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom generators can break casual #66
Comments
I looked at the code and I think this is happening because the text provider has some helper properties that aren't part of the public api but they do get mixed into the |
To resolve this we can change providers +var privateHelper = 'blah';
var provider = {
- privateHelper: 'blah',
builtInGenerator: function() {
- return this.privateHelper;
+ return privateHelper;
}
}; |
Is there any movement on this? |
None as far as I know.
I'm just working around it in my project.
…On Fri, Jun 19, 2020, 7:08 AM Craig ***@***.***> wrote:
Is there any movement on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#66 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA6IMA5E2NI2JRSXWYSMF3RXNBJBANCNFSM4DJV365A>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Defining a custom generator with specific names can break other casual generators.
Example:
It only happens for me when custom generator named "letters" and it takes an argument.
The text was updated successfully, but these errors were encountered: