---
# System prepended metadata

title: Nushell core team meeting 2025-06-04

---

# Nushell core team meeting 2025-06-04
## Attendees
- Darren
- Rose
- Michael
- Douglas
- Jack
- Bahex
- 

## Agenda
- [X] {%preview https://github.com/nushell/nushell/pull/15878 %}
  possibly add explicit support for `--` as a "parameter terminator"

  ```nu
  def foo [--foo, --bar, --, ...rest] {}
  ```

  `...rest` would be treated similarly to the rest parameter in `def --wrapped` commands

- [X] `table` rename
    - are we sticking with `render`?
    - primitive value REPL representation change
- [ ] More robust error handling, allowing users to attach error codes ([context](https://discord.com/channels/601130461678272522/601130461678272524/1378572493207507005))
- [X] Release volunteers

## Discussed Topics

- hold off on #15878 out of an abundance of caution (unless we can get someone who can do a patch release)

## `table` -> `render`
- we generally like using the same styling inside and outside of tables
  - will have to more carefully consider datetimes
- converting all values to string makes the `render` name make more sense
- idea: have `render` subcommands for different frontends
    - `render terminal`, `render notebook`/`render jupyter`, `render nana`, `render html`, `render gui`
    - automatically choose correct frontend when just typing `render`
    - how to avoid having to type out `render terminal` for table options?
      - ship `alias rt = render terminal`: not ideal
      - automatically forward flags from `render` to appropriate frontend: what if flags aren't supported by frontend, or are different between frontends?
      - make `table` command set metadata which is consumed by `render`: if you need to render to string, not much shorter than `render terminal`, and still keeps (slightly less) confusingly-named `table` command
        - on the name point, maybe this could be `style table`, along with other metadata styled things? that is even longer though
      a
    - does this idea hastily couple creating "human-readable values" and "rendering to fr
      - `render` would have to have output type `any`, making it difficult to reason about its output
      - this use-case isn't very well understood right now
    