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

refactor: Make the metadata dynamic via implementing JsonString #4732

Merged

Conversation

Stukalov-A-M
Copy link
Contributor

Description

  • Removed MetadataValueBox
  • Added JsonString

Linked issue

Benefits

Checklist

  • I've read CONTRIBUTING.md
  • I've used the standard signed-off commit format (or will squash just before merging)
  • All applicable CI checks pass (or I promised to make them pass later)
  • (optional) I've written unit tests for the code changes
  • I replied to all comments after code review, marking all implemented changes with thumbs up

@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch from 737bc02 to 3841f56 Compare June 14, 2024 10:12
@github-actions github-actions bot added the api-changes Changes in the API for client libraries label Jun 14, 2024
@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch 2 times, most recently from b130a1b to 0366522 Compare June 14, 2024 10:50
@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch from 0366522 to 58064de Compare June 14, 2024 11:53
@nxsaken
Copy link
Contributor

nxsaken commented Jun 14, 2024

Please use the imperative mood in commit messages / PR titles to keep it consistent

@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch 3 times, most recently from 65fb73a to 6bd36fd Compare June 16, 2024 19:49
@Stukalov-A-M Stukalov-A-M changed the title refactor: Metadata became dynamic and consists of JsonString refactor: Make the metadata dynamic via implementing JsonString Jun 16, 2024
@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch from 6bd36fd to 84ecc99 Compare June 16, 2024 19:55
@Stukalov-A-M Stukalov-A-M requested a review from mversic June 16, 2024 19:56
@Stukalov-A-M
Copy link
Contributor Author

Created a a task for unit tests creation
#4748

@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch 2 times, most recently from 710d238 to 1ed9e5b Compare June 27, 2024 07:45
@Stukalov-A-M Stukalov-A-M force-pushed the dynamic-metadata-values branch from 1ed9e5b to 399fd81 Compare June 27, 2024 08:33
@mversic
Copy link
Contributor

mversic commented Jun 27, 2024

@Stukalov-A-M IMO you can add #[ignore to the failing test and fix it in a separate PR

@Stukalov-A-M Stukalov-A-M merged commit db96164 into hyperledger-iroha:main Jun 27, 2024
9 of 11 checks passed
@Stukalov-A-M Stukalov-A-M deleted the dynamic-metadata-values branch June 27, 2024 09:00
@nxsaken
Copy link
Contributor

nxsaken commented Jun 28, 2024

@Stukalov-A-M the integration test correct_pagination_assets_after_creating_new_one has been failing since merging this. Can you fix or ignore the test as suggested above?

@Stukalov-A-M
Copy link
Contributor Author

@Stukalov-A-M the integration test correct_pagination_assets_after_creating_new_one has been failing since merging this. Can you fix or ignore the test as suggested above?

I don't think it's possible in the closed PR. You may add ignore if u have an opened PR.

hollermay pushed a commit to hollermay/iroha that referenced this pull request Jun 28, 2024
@nxsaken
Copy link
Contributor

nxsaken commented Jul 1, 2024

@Stukalov-A-M I meant in a separate PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-changes Changes in the API for client libraries
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dynamic metadata value
4 participants