nushell/crates/nu-path/Cargo.toml

[package]
authors = ["The Nushell Project Developers"]
description = "Path handling library for Nushell"
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-path"
edition = "2021"
license = "MIT"
name = "nu-path"
version = "0.96.2"
exclude = ["/fuzz"]

[lib]
bench = false

[dependencies]
dirs = { workspace = true }

[target.'cfg(windows)'.dependencies]
omnipath = { workspace = true }

[target.'cfg(all(unix, not(target_os = "macos"), not(target_os = "android")))'.dependencies]
pwd = { workspace = true }
Move path handling to nu-path (#3653) * fixes #3616 2021-06-20 01:07:26 +02:00			`[package]`
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 19:30:27 +01:00			`authors = ["The Nushell Project Developers"]`
nu-path crate refactor (#3730) * Resolve rebase artifacts * Remove leftover dependencies on removed feature * Remove unnecessary 'pub' * Start taking notes and fooling around * Split canonicalize to two versions; Add TODOs One that takes `relative_to` and one that doesn't. More TODO notes. * Merge absolutize to and rename resolve_dots * Add custom absolutize fn and use it in path expand * Convert a couple of dunce::canonicalize to ours * Update nu-path description * Replace all canonicalize with nu-path version * Remove leftover dunce dependencies * Fix broken autocd with trailing slash Trailing slash is preserved only in paths that do not contain "." or "..". This should be fixed in the future to cover all paths but for now it at least covers basic cases. * Use dunce::canonicalize for canonicalizing * Alow cd recovery from non-existent cwd * Disable removed canonicalize functionality tests Remove unused import * Break down nu-path into separate modules * Remove unused public imports * Remove abundant cow mapping * Fix clippy warning * Reformulate old canonicalize tests to expand_path They wouldn't work with the new canonicalize. * Canonicalize also ~ and ndots; Unify path joining Also, add doc comments in nu_path::expansions. * Add comment * Avoid expanding ndots if path is not valid UTF-8 With this change, no lossy path->string conversion should happen in the nu-path crate. * Fmt * Slight expand_tilde refactor; Add doc comments * Start nu-path integration tests * Add tests TODO * Fix docstring typo * Fix some doc strings * Add README for nu-path crate * Add a couple of canonicalize tests * Add nu-path integration tests * Add trim trailing slashes tests * Update nu-path dependency * Remove unused import * Regenerate lockfile 2021-08-28 14:59:09 +02:00			`description = "Path handling library for Nushell"`
Add repository info to all workspace crates (#6320) This helps people who find these crates on crates.io 2022-08-14 14:21:20 +02:00			`repository = "https://github.com/nushell/nushell/tree/main/crates/nu-path"`
update all cargo crates to edition 2021 (#781) 2022-01-20 14:13:45 +01:00			`edition = "2021"`
Add 'from json' 2021-10-01 07:11:49 +02:00			`license = "MIT"`
			`name = "nu-path"`
Bump version to `0.96.2` (#13485) This should be the new development version. We most likely don't need a 0.96.2 patch release. Should be free to merge PRs after this. 2024-07-30 02:20:55 +02:00			`version = "0.96.2"`
Add 2 fuzzers for nu-path, nu-parser (#10376) # Description This PR adds a fuzzer for the nu-path and the nu-parser crate. Now you can go to `crates/nu-path/fuzz`/`crates/nu-parser/fuzz` and run `cargo fuzz` to find crashes. https://github.com/nushell/nushell/issues/10365 and #9417 was found by this --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com> 2023-09-16 22:32:53 +02:00			`exclude = ["/fuzz"]`
Move path handling to nu-path (#3653) * fixes #3616 2021-06-20 01:07:26 +02:00
Disable auto-benchmark harness for crates (#8057) # Description This disables automatic detection of `#[bench]` and other benchmarks within the crates. Our benchmarks should all live in `benches` This fixes a problem with criterion flags and should also reduce the build requirements for `cargo bench` a bit Taken from https://github.com/nushell/nushell/pull/7952 See: https://bheisler.github.io/criterion.rs/book/faq.html#cargo-bench-gives-unrecognized-option-errors-for-valid-command-line-options # User-Facing Changes None 2023-02-12 23:22:00 +01:00			`[lib]`
			`bench = false`

Move path handling to nu-path (#3653) * fixes #3616 2021-06-20 01:07:26 +02:00			`[dependencies]`
Switch from dirs_next 2.0 to dirs 5.0 (#13384) <!-- 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. --> Replaces the `dirs_next` family of crates with `dirs`. `dirs_next` was born when the `dirs` crates were abandoned three years ago, but they're being maintained again and most projects depend on `dirs` nowadays. `dirs_next` has been abandoned since. This came up while working on https://github.com/nushell/nushell/pull/13382. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> None. # 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 > ``` --> Tests and formatter have been run. # 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. --> 2024-07-16 14:16:26 +02:00			`dirs = { workspace = true }`
Remove unused dependencies (#6945) * Remove unused dependencies Inspired by #6938 ran `cargo +nightly udeps --features extra`. Removes 2 crates and should remove an unnecessary intra-workspace dependency which might open up further opportunities for compilation. * Make windows-only dependency conditional in toml `omnipath` is only used on Windows and already behind a `#[cfg]` block in the code. Made the dependency in `Cargo.toml` conditional as well. * Make `nu-pretty-hex` example a proper example This allows making `rand` a dev-dependency in this crate. 2022-10-29 21:19:12 +02:00
			`[target.'cfg(windows)'.dependencies]`
Move more dependencies to workspace level (#12270) # Description This is a followup to #12043 that moves more dependency versions to workspace dependencies. # User-Facing Changes N/A # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` 2024-03-24 00:46:02 +01:00			`omnipath = { workspace = true }`
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed. 2022-04-25 00:12:57 +02:00
Support Termux (#10013) 2023-08-28 08:53:25 +02:00			`[target.'cfg(all(unix, not(target_os = "macos"), not(target_os = "android")))'.dependencies]`
Bump version to `0.96.0` (#13433) 2024-07-24 01:10:35 +02:00			`pwd = { workspace = true }`