-
Notifications
You must be signed in to change notification settings - Fork 13
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
typehole.tNaN #7
Comments
If I reload the window, the issue does not occur. So it seems to me that perhaps there's some kind of caching issue that is resolved when the editor is reloaded? Clearing out all type holes from the project doesn't fix it... a reload is required. |
👋 It must have been Typehole's internal state and the overly naive implementation for figuring out an id for the next hole based on the previous ids. If one of the previous ids were not possible to parse to an integer, then Thanks for the video and a good issue description. Much appreciated |
Should now be fixed in 1.5.1. |
It seems if you add a new typehole that doesn't have the "typehole.t[number] format, the next typehole you'll add with cmd+. will cause the name if the whole to be tNaN.
I think a possible solution for this would be to just treat the method labels as strings
The text was updated successfully, but these errors were encountered: