extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2025-04-29 15:44:28 +02:00
Code Issues Packages Projects Releases Wiki Activity
208ebeefab
nushell/crates/nu-std/std-rfc
History
Tyarel 6193679dfc
Fix kv set with a closure argument (#15588) 
<!--
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!
-->
Fixes #15528 
# Description
Fixed `kv set` passing the pipeline input to the closure instead of the
value stored in that key.

# User-Facing Changes
Now `kv set` will pass the value in that key to the closure.

# Tests + Formatting


# After Submitting
2025-04-22 22:30:38 +08:00
..
clip Fixes clip copy stripping control characters when de-ansifying (#15428) 2025-03-28 19:15:17 -04:00
conversions docs(std-rfc): use actual examples rather than doc comments (#15097) 2025-02-11 16:33:27 -06:00
kv Fix kv set with a closure argument (#15588) 2025-04-22 22:30:38 +08:00
path docs(std-rfc): use actual examples rather than doc comments (#15097) 2025-02-11 16:33:27 -06:00
str docs(std-rfc): use actual examples rather than doc comments (#15097) 2025-02-11 16:33:27 -06:00
tables refactor: tree-sitter-nu friendly alternative expressions (#15301) 2025-03-12 08:48:19 -05:00
mod.nu Move std-rfc into Nushell (#15042) 2025-02-09 09:03:37 -05:00
README.md Update README.md 2025-02-10 09:06:09 -05:00

README.md

std-rfc

Overview and Requirements

This module includes potential candidate commands (and other definitions) for inclusion in the Standard Library (std) that is built in to Nushell. As a general guideline, candidates should:

  • Be general purpose features that will be useful to a number of users
  • Include doc comments for definitions and parameters that can be used with help <command>
  • Include tests
  • Since doc comments are fairly limited, additional documentation can be included in a GitHub discussion. This documentation can then be moved to the main website when the feature is promoted to std. See this example for some table helpers.

Showcase and Discussion

While primary feedback should take place in the PR, we have also established a Drawing Board Discord channel which can be used for several purposes:

  • Ideation before a PR is submitted
  • Raise awareness of the feature
  • Short-term questions and discussion

Note: The Drawing Board is not just for std-rfc. Please tag your topic with std-library if it is about a Standard Library idea.

Promotion Evaluation

In general, new std-rfc features will be evaluated after they have been trialed for a sufficient period, which may vary depending on the feature. After that period, the feature may be:

  • Promoted to std
  • Removed from std-rfc
  • Or changes may be requested and then reevaluated later