First Release Checklist

[nvarner]

Thanks to the many PRs we're getting, the LSP is nearly ready for its first release! Here's what has to happen first:

• Decide on a name (depends on getting a response on Discord about the word "Typst")
• Tooling, linting, and formatting configuration
  • Merge TypeScript lints from the preview branch (if not covered by add release action #7)
  • Add prettier support to TS (Add prettier and format files #16)
• Add CI support to ensure future PRs compile with high-quality code, deployments happen automatically, etc
  • Merge CI: add a job to cargo check and cargo fmt pull requests #12
  • Merge add release action #7
  • Add CI support for Typescript in the extension
  • Add CI support for running Rust and TS tests (which do not yet exist, but will need to in the near future)
  • Run Clippy on Rust code
• Fix critical bugs
  • Merge fix: file path resolution on Windows #9
  • Merge handle open and close events #13
• Prepare for deployment!
  • Get credentials for VS Code Marketplace
  • Add support for Open VSX

If anyone would like to suggest a name, please feel free to do so here.

[astrale-sharp]

• Add prettier support to TS
  as a means to format typst code?
• Tooling, linting, and formatting configuration
  I Feel like this is something the community is working on (a package manager was mentionned here

Ideally they might be crates depending on typst as well which would make them quite easy to integrate.

This will take time tho, I would be in favor of publishing without waiting for good tools, after all typst is still in beta.

[nvarner]

Sorry, that might have been unclear. I meant to integrate tooling, linting, and formatting for the source code of the LSP.

For example, prettier is a formatter for TypeScript. Integrating it here means all the extension source code will have consistent formatting.

[nvarner]

Formatting, linting, etc are long-term goals to provide to Typst, but certainly not release blockers :)

[astrale-sharp]

great :)

[beeb]

For the formatting, I would be partisan of making it both a lib crate and a binary that can be run on any number of input files just like rustfmt. The library could then be included in the LSP and the binary could be distributed for people to use in CI etc.

I started looking into making a formatter this afternoon but I have never done something like this and it's a daunting task. I have the SyntaxNode tree but then to enforce rules on this is no easy task for me. In case of a breakthrough I'll make it public.

[astrale-sharp]

I start working on it today, feel free to discuss it on the discord with me ;)

[beeb]

Cool! I started working on "compile-on-save" vs "compile-on-type"

[laurmaedje]

Hey, this is Laurenz from Typst. Thanks for asking about the name and logo!

You are free to use the name "Typst LSP", but only in a non-commercial context. The same holds true for the Typst logo. If you use it, please reproduce it accurately (colors/fonts). You can use the version from our website. Should you decide to create a modified version of the logo, please do it in a way that makes it clearly distinguishable from our logo.

For all commercial usages of our name or logo, you would need to obtain permission from us.

[nvarner]

That's great to hear. Thank you!

I have no intention to commercialize the LSP or extension, so I'll stick with the name.

[laurmaedje]

I have no intention to commercialize the LSP or extension, so I'll stick with the name.

I figured as much, just wanted to state this here for the sake of completeness. :)

[nvarner]

We've released!

https://open-vsx.org/extension/nvarner/typst-lsp
https://marketplace.visualstudio.com/items?itemName=nvarner.typst-lsp