-
Notifications
You must be signed in to change notification settings - Fork 29
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
Verify origins do not collide with ServiceActor::Result
object methods
#138
Verify origins do not collide with ServiceActor::Result
object methods
#138
Conversation
I tweaked implementation and not the total list of "dangerous" methods is much shorter:
But one issue still remains, using these symbols in inputs/outputs/aliases will trigger the warning AND will
In latest release (3.7.0) cc @sunny |
That is awesome. 😍 Kudos on using a BasicObject yet adding the basic methods it would need.
Oh, you’re right. So perhaps this should simply raise an ArgumentError straight away as the current behavior is already impacter. Now that the list of methods is smaller I don’t think we need a warning here. |
Excellent! Not only does this warn of collisions it actually reduces it thanks to the SimpleObject. 👏🏻 |
@sunny I encountered a specific but crucial bug related to this PR. Gonna try to fix it soon |
Resolves #137
I'm not sure about removing display-related tests and code, but since we do not allow these methods in inputs/outputs seems like we dont have to be specific about
display
Also added some tests and removed lonely
require ostruct