mirror of
https://github.com/nushell/nushell.git
synced 2024-11-25 09:53:43 +01:00
055d7e27e9
<!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> @sholderbach mentioned that I introduced `convert_case` as a dependency while we already had `heck` for case conversion. So in this PR replaced the use `convert_case` with `heck`. Mostly I rebuilt the `convert_case` API with `heck` to work with it as I like the API of `convert_case` more than `heck`. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> Nothing changed, the use of `convert_case` wasn't exposed anywhere and all case conversions are still available. # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use toolkit.nu; toolkit test stdlib"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> No new tests required but my tests in `test_derive` captured some errors I made while developing this change, (hurray, tests work 🎉) - 🟢 `toolkit fmt` - 🟢 `toolkit clippy` - 🟢 `toolkit test` - 🟢 `toolkit test stdlib` # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. -->
21 lines
607 B
TOML
21 lines
607 B
TOML
[package]
|
|
authors = ["The Nushell Project Developers"]
|
|
description = "Macros implementation of #[derive(FromValue, IntoValue)]"
|
|
edition = "2021"
|
|
license = "MIT"
|
|
name = "nu-derive-value"
|
|
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-derive-value"
|
|
version = "0.97.2"
|
|
|
|
[lib]
|
|
proc-macro = true
|
|
# we can only use exposed macros in doctests really,
|
|
# so we cannot test anything useful in a doctest
|
|
doctest = false
|
|
|
|
[dependencies]
|
|
proc-macro2 = { workspace = true }
|
|
syn = { workspace = true }
|
|
quote = { workspace = true }
|
|
proc-macro-error = { workspace = true }
|
|
heck = { workspace = true } |