-
Notifications
You must be signed in to change notification settings - Fork 55
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
Node.SetProperty Only Allows String Properties #73
Comments
+1 |
@jmcvetta unfortunately changing the sig from string to interface{} will not be backward compatible. I can send a pull request, but to be backward compatible, i will have to add a new method - if u like that - whats a good name for the method for code convention... |
@brad-ross-35 in the meantime i just implemented the method myself - if u need here u go.. please note to test in ur env and production...
|
Thanks! I found a way around the problem, but hopefully there will be a patch soon--backwards compatibility shouldn't be a big issue, and I'm sure people using the library would rather account for the change than go on without being able to use non-string properties. |
Please feel free to submit a Pull Request with your suggested changes. Contributions are happily accepted! |
The function signature of
Node.SetProperty
is as follows:I would like my
value
to be abool
. Can you make the type ofvalue
beinterface{}
? You should be able to deal with non-string properties as you do when you pass aneoism.Props
struct toNode.SetProperties
...The text was updated successfully, but these errors were encountered: