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

test Spawn cargo add #3

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

test Spawn cargo add #3

wants to merge 6 commits into from

Conversation

tomasol
Copy link
Owner

@tomasol tomasol commented Jan 12, 2024

No description provided.

peterhuene and others added 3 commits January 11, 2024 21:41
This commit updates crate dependencies to latest.

It also fixes test failures introduced by the latest Rust toolchain.

Tests are now put in a temporary directory instead of under `target`, which
helps isolate the tests from one another.
…liance#205)

Add `--workspace` and `--all-targets` switches to both vscode
and emacs configs, that are generated in `cargo component new`.
This is in line with what rust-analyzer uses when
`rust-analyzer.check.overrideCommand` is empty.
…dealliance#206)

* Try to use current package in the `add` command

Add test `two_projects_in_one_workspace_validate_add_from_path` which
cretes two projects in the same workspace. Run `cargo workspace add`
in each of those projects without `--package` switch to check we are
modifying the correct project/package.

* Use `find_current_package_spec` in `publish` command
…#211)

This commit renames the `--reactor` option for the `new` subcommand to `--lib`.

It maintains an alias of `--reactor` for backwards compatibility.

Updated the tests to use `--lib` and added a test to ensure `--reactor` is
still respected.

Closes bytecodealliance#198.
This commit is a breaking change to `cargo-component` with the intention of
improving component build time (now down to two transitive crate dependencies)
and get `rust-analyzer` fully working with bindings.

It removes the `cargo_component_bindings` and `cargo_component_macro` crates.
Instead of using a macro for including the generated bindings,
`cargo-component` now directly writes to a `src/bindings.rs` file which is
included as a submodule in `main.rs` or `lib.rs`.

Additionally, the `update` subcommand was removed as it is no longer necessary
since there is no `cargo_component_bindings` crate referenced in `Cargo.toml`;
the functionality to update `cargo-component` itself can simply be replaced
with a `cargo install` or `cargo binstall`.

Closes bytecodealliance#210.
@peterhuene peterhuene force-pushed the spawn-cargo-add branch 2 times, most recently from 07ed8c9 to 1064284 Compare January 25, 2024 23:20
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.

2 participants