-
Notifications
You must be signed in to change notification settings - Fork 276
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
Split data model #4552
Labels
question
Further information is requested
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
logically, there is 3 apis:
4th is executor foreign functions and their payload. This one shouldn't be mixed with the previous ones. And this one doesn't have to be stabilized for the time being because it is low level and user is always required to use some of the provided macros to.
5th is
iroha_schema
where we could also say that schema doesn't need to be stabilized because users will always be required to use one of iroha clients but here I don't find that argument entirely convincingProposed changes
not sure. Let's figure out what is the scope of change needed here and if we need to do some refactoring
Motivation
structs and APIs that cannot be used by client shouldn't be accessible by the client, etc.
The text was updated successfully, but these errors were encountered: