Skip to content

Conversation

@decentralgabe
Copy link
Contributor

No description provided.


- name: Cargo publish dry run
env:
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@paolodamico will need your help with this

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove, a token is not needed. publishing should only be done with trusted publishing


- name: Run Rust tests
run: cargo test --package idkit-core
run: cargo test --package idkit --all-features
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you probably also want to run tests with --no-default-features

```
┌─────────────────────────────────────┐
│ Rust Core (idkit-core)
│ Rust Core (idkit)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm shouldn't foreign bindings still inherit from idkit-core? so idkit-core (Rust package) -> idkit-js (with react), idkit-swift, idkit-kotlin

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah it's just a naming thing, I made it idkit so the rust package is idkit not idkit core, even though it is core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants