Skip to content
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

Type hinting / contract hinting #30

Closed
must opened this issue Aug 22, 2018 · 2 comments
Closed

Type hinting / contract hinting #30

must opened this issue Aug 22, 2018 · 2 comments

Comments

@must
Copy link
Member

must commented Aug 22, 2018

As an analogy to interfaces in Object Oriented Programming languages, it would provide a basis for best practice coding when there's a kind of type check on each call made out to nodes.

@loreanvictor
Copy link
Collaborator

this is a duplicate of #11.

@must
Copy link
Member Author

must commented Aug 23, 2018

Just as a little difference to the other issue. I'm talking more type hinting as objects (since most of what's passing is JSON rather than simple types). So it's to be taken into consideration that type hinting as interfaces (again analogy to OOP) could be a powerful way and an extension of the suggestion mentioned in issue #11. Of course this is the be approached carefully as it can add unnecessary clutter and complexity to the platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants