Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ add a Contributing guide to parser and editor tools related stuff #1311

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .vuepress/configs/sidebar/en.ts
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,7 @@ export const sidebarEn: SidebarConfig = {
'commands',
'plugins',
'plugin_protocol_reference',
'parser_and_other_editor_tools.md',
],
},
],
Expand Down
77 changes: 77 additions & 0 deletions contributor-book/parser_and_other_editor_tools.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
---
title: Parser and other editor tools
---

# Parser and other editor tools

Hi! There is a lot of space to grow in this area, and the development is
somewhat spaced in time, so I (@AucaCoyan) decided to make a document explaning
the framework, conventions and other required knowledge to help others and
myself with this section.

## Parser

The most important piece of this chapter is the parser. The parser is the bridge
between the `*.nu` text files and the internal representation of object in
nushell. Almost everything in this chapter interacts or is affected by the
parser.

### Current status

The current production parser is not bad at all, but it has certain areas that
some improvement that could be greately appreciated. Sophia [started a new parser](https://github.com/sophiajt/new-nu-parser/)
and it's still on the works. The central idea of this new parser is that it
will have multiple passes over the text, improving the typing structures by
a lot.

## Formatter

We have [`nufmt`](https://github.com/nushell/nufmt), but is a little stagnated
because it will probably need some rework after the new parser is landed. The
current issue is a bug reading stdin from the cmdline. Ask @AucaCoyan anything!

## LSPs

LSP stands for Language Server Protocol, a [Microsoft document](https://microsoft.github.io/language-server-protocol/)
to establish communication between text editors and parsers and other tools.

We currently have 2 of them, one for VS Code and one for other terminal editors

### VSCode

This has [it's own extension](https://github.com/nushell/vscode-nushell-lang/)
and it's the most advanced LSP. It was the first to appear it is bootstraped
from a prototype of Microsoft. It's written in Typescript and interacts with
`nu` in the command line to have:

- hover
- go to definition
- auto-completions
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few things missing from this list.
It also helps locate nu and if it finds it allow nu to be used as a terminal shell.
It displays Inlays
It allows you to have separate IncludeDirs
It has diagnostics to show errors

Most of this is laid out in the extension readme


### nu-lsp

This is a newer LSP that we would like to have as the long term for every editor
. It's written in rust and it's on the `nushell/nushell` repo, in the
[`crates/nu-lsp`](https://github.com/nushell/nushell/tree/main/crates/nu-lsp)
folder. Interacts via stdin and stdout and it is useful for vim,
neovim, helix and other text editors. Sadly, it doesn't have the same level of
features of VSCode-nushell-lang, that's why we still can't replace it.

## Tree-sitter

For syntax highligting we can use [nushell tre-sitter grammar](https://github.com/nushell/tree-sitter-nu)
AucaCoyan marked this conversation as resolved.
Show resolved Hide resolved
this is useful for terminal text editors (nvim, helix, etc), VS Code [has
its own grammar](https://github.com/nushell/vscode-nushell-lang/blob/main/syntaxes/nushell.tmLanguage.json)

## I dont know a thing about all this, can you give me a hint where to learn?

Sure!

- Adrian Hesketh gives an excellent talk about [how LSP works](https://youtu.be/EkK8Jxjj95s?si=KT3YdfV5LebbTzXp)
- TeeJ explains [tree-sitter in a 15 min video](https://www.youtube.com/watch?v=09-9LltqWLY)
- about the formatter:
- Bob Nystrom worked with the dart formatter and [wrote a precious blog post](https://journal.stuffwithstuff.com/2015/09/08/the-hardest-program-ive-ever-written/) about his journey. The hackernews
[post is also useful](https://news.ycombinator.com/item?id=22706242) for the
comments!
- and a [short overall view](https://blog.vjeux.com/2017/javascript/anatomy-of-a-javascript-pretty-printer.html)
of how `prettier` works
24 changes: 23 additions & 1 deletion i18n-meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,17 @@
"pt-BR": "-",
"ru": "-"
},
{
"name": "cheat_sheet.md",
"en": "In progress",
"zh-CN": "-",
"de": "-",
"tr": "-",
"ja": "-",
"es": "-",
"pt-BR": "-",
"ru": "-"
},
{
"name": "coloring_and_theming.md",
"en": "Completed",
Expand Down Expand Up @@ -549,6 +560,17 @@
"pt-BR": "-",
"ru": "-"
},
{
"name": "style_guide.md",
"en": "In progress",
"zh-CN": "-",
"de": "-",
"tr": "-",
"ja": "-",
"es": "-",
"pt-BR": "-",
"ru": "-"
},
{
"name": "table_of_contents.md",
"en": "Completed",
Expand Down Expand Up @@ -637,4 +659,4 @@
"pt-BR": "-",
"ru": "-"
}
]
]