-
Notifications
You must be signed in to change notification settings - Fork 27
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
Backport: Standardize JSON formatting of action data #466
Comments
This change needs to be done at a major release point and clearly communicated. It affects all clients as it changes the JSON format. |
Not saving to |
Repository owner
moved this from Todo
to Done
in ENF Engineering
Jul 12, 2022
stephenpdeos
removed
the
planning
Propose change to milestone in next planning meeting
label
Jul 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Those two should go together.
EOSIO/eos#10100
old code doing this:
act.data ------can parse to json object ? if yes "data"=json object and hex_data = "hex string"
if no "data" = "hex string"
new code doing this:
act.data ------can parse to json object ? if yes "data"=json object and hex_data = "hex string"
if no "hex_data" = "hex string"
and extract function also some changes correspondingly.
Also, please see related test PR here:
EOSIO/eos#10405
The text was updated successfully, but these errors were encountered: