-
Notifications
You must be signed in to change notification settings - Fork 42
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
Protocol based on serde #2161
base: master
Are you sure you want to change the base?
Protocol based on serde #2161
Conversation
f8aa677
to
e005959
Compare
39a7b03
to
6140ba9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great 👏
I've found minor issues and added some suggestions.
I'll provide the needed changes on the build CLI tool once the other PR is merged and master is merged here.
There is another point about Macros Hygiene that can be adjusted (optionally since the macro are for internal use only). But if we want to make the macro hygiene we may need to use full paths on every type inside the macros up to $crate::
for crate types or ::std::
for rust standard library types
application/apps/indexer/stypes/src/command/folders/extending.rs
Outdated
Show resolved
Hide resolved
cd ../../rustcore/ts-bindings | ||
rm -rf ./node_modules | ||
rm -rf ./spec/build | ||
rake bindings:test:protocol |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to replace this rake call with a function on the build CLI tool before merging or directly after that, to avoid the dependency on Ruby tooling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sure... will do it as soon as build cli will be updated
9dac3ad
to
6fc4a2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks amazing, great job! 💯
I'll provide the needed implementation on the build CLI tool and add them to this PR ASAP
* Adjust dependencies resolving to include protocol build on test jobs. * Add unit test to ensure involved targets are built on bindings tests. * Adjust integration tests accordingly.
CI is failing now because it still using the previous Tool version and not using the latest one. link |
Remove temp fix from GitHub action after fixing the main issue in build CLI tool
5c696d3
to
4d9775f
Compare
* Generate typescript files only on running tests with feature `test_and_gen` activated.
The same feature `test_and_gen` is used for both generating types and running prop tests. By marking prop tests as ignored we are able to generate the files without running the extensive prop tests
@DmitryAstafyev I've fixed generating typescript files on each test call by adding the feature Then I ran into an issue that the prop tests will be triggered each time we want to generate new types, so I marked them is ignored to be ran explicitly with the |
Implementation of protocol for communication between
rust
andnodejs
based onserde
+bincode
.