# Nushell core team meeting 2024-01-17
## Attendees
- Jakub
- Ian
- Michael
- Antoine
- Edhowland
- Darren

## Agenda
- [x] @Ian: `from json --strict`/`from hjson` [issue #11548](https://github.com/nushell/nushell/issues/11548)
- [x] Thinking about documentation: Split book into reference + book
- [x] 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](https://hackmd.io/hLTipwOaR2K28GzwHrtVGQ) as a starter.

### Debugger

Could we support DAP?

Here is a reference in Rust...

[A native debugger extension for VSCode based on LLDB](https://github.com/vadimcn/codelldb)

[DAP Reference](https://microsoft.github.io/debug-adapter-protocol//)

## Issues
> :bulb: the issues which [needs-core-team-attention](https://github.com/nushell/nushell/labels/needs-core-team-attention)

> :bulb: **Note**
> to list all the PRs currently [opened in `nushell/nushell`](https://github.com/nushell/nushell/pulls):
> ```nu
> gh pr list --json url,number,author,title
> | from json
> | each {|i|
> $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
> }
> | reverse
> | to text
> ```