nushell/tests
Anton 7221eb7f39
Fix typos and use more idiomatic assertions (#7755)
I have changed `assert!(a == b)` calls to `assert_eq!(a, b)`, which give
better error messages. Similarly for `assert!(a != b)` and
`assert_ne!(a, b)`. Basically all instances were comparing primitives
(string slices or integers), so there is no loss of generality from
special-case macros,

I have also fixed a number of typos in comments, variable names, and a
few user-facing messages.
2023-01-15 15:03:32 +13:00
..
assets/nu_json Remove old nushell/merge engine-q 2022-02-07 14:54:06 -05:00
const_ Initial support for parse-time constants (#7436) 2022-12-22 00:21:03 +02:00
fixtures Auto-Completion: put ` tildes around filenames with parentheses (#7712) 2023-01-10 20:41:54 +01:00
hooks Fix typos and use more idiomatic assertions (#7755) 2023-01-15 15:03:32 +13:00
modules Expand Nushell's help system (#7611) 2022-12-30 17:44:37 +02:00
overlays Fix typos and use more idiomatic assertions (#7755) 2023-01-15 15:03:32 +13:00
parsing Revert "Primitives now use color closures..." (#7710) 2023-01-08 21:53:52 -08:00
path Run a round of clippy --fix to fix a ton of lints (#7006) 2022-11-04 15:11:17 -05:00
plugins Feature cleanup (#7182) 2022-11-22 16:58:11 -08:00
scope Fix reporting of which and $nu.scope (#4836) 2022-03-13 21:32:46 +02:00
shell Revert "Primitives now use color closures..." (#7710) 2023-01-08 21:53:52 -08:00
main.rs Initial support for parse-time constants (#7436) 2022-12-22 00:21:03 +02:00