-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat: add re exports from base used in public api #394
feat: add re exports from base used in public api #394
Conversation
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.
Looks good! Thank you! I left some comments inline.
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.
Looks good! Thank you! I would move Felt
, StarkField
, and Word
into the root, but other than that, we can merge.
cd9f09d
to
4945a84
Compare
In order to test this, I replicated the changes from this commit into `mFragaBA-workspace-refactor`, and tried making the integration tests compile without using miden-objects nor miden-tx as a dependency.
added more re-exports based on what I saw being imported in the [wasm fork](https://github.com/demox-labs/miden-client/).
4945a84
to
a16225c
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.
LGTM!
* refactor: add refactors from miden-objects and miden-tx * feat: add miden base re-exports on library crate In order to test this, I replicated the changes from this commit into `mFragaBA-workspace-refactor`, and tried making the integration tests compile without using miden-objects nor miden-tx as a dependency. * feat: add more miden base re-exports on library crate added more re-exports based on what I saw being imported in the [wasm fork](https://github.com/demox-labs/miden-client/). * refactor: flatten re-exports * address comments from review
closes #280
Tested with:
mFragaBA-workspace-refactor
which refactors the single crate structure into a miden-cli, miden-client and tests subcrates. This made it easier to test the usage of the client library as a dependency of the integration tests. I added it as a dependency (and didn't add miden-objects nor miden-tx) and added missing re-exports if any until it compiled.I think testing against real use cases instead of just looking at the api will avoid some missing re-exports problems. We can still iterate on this as users of the crate can decide when they remove the dependency and just use the re-exports instead.