Nushell core team meeting 2024-01-17

Attendees

• Jakub
• Ian
• Michael
• Antoine
• Edhowland
• Darren

Agenda

• @Ian: from json --strict/from hjson issue #11548
• Thinking about documentation: Split book into reference + book
• I think I figured out how to implement in-engine debugger
  • Requirement: No instrumentation in the hot path, non-debugging code paths should have zero perf impact
  • Might have some increase in binary size due to generics (tried to mitigate with trait objects)

Discussed Topics

Issue 11548

We're fine with adding strict json parsing, leaning towards --strict flag for now.

Reference Book Initial Draft

Let's create a new Reference book with the Language guide as a starter.

Debugger

Could we support DAP?

Here is a reference in Rust…

A native debugger extension for VSCode based on LLDB

DAP Reference

Issues

Image Not Showing Possible Reasons

• The image file may be corrupted
• The server hosting the image is unavailable
• The image path is incorrect
• The image format is not supported

Learn More →

the issues which needs-core-team-attention

Image Not Showing Possible Reasons

• The image file may be corrupted
• The server hosting the image is unavailable
• The image path is incorrect
• The image format is not supported

Learn More →

Note
to list all the PRs currently opened in nushell/nushell:

gh pr list --json url,number,author,title
| from json
| each {|i|
    $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
}
| reverse
| to text