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

Release 2.0.0 #47

Merged
merged 59 commits into from
Sep 8, 2023
Merged

Release 2.0.0 #47

merged 59 commits into from
Sep 8, 2023

Conversation

zm-cttae
Copy link
Member

@zm-cttae zm-cttae commented Sep 8, 2023

🏗️ Pull Request

  • Used a clear / meaningful title for this pull request.
  • Tested the changes on your own grammar (on your projects).
  • Added / Edited tests to reflect changes (test folder).
  • Have read the Contributing part of the README.
  • Passed npm test.
  • I noted my changes in the pull request body and/or changelog.

👷🏾‍♀️ Fixes

Part of #46 epic.

Description

Expose language scope, range, token & configuration APIs. Make vscode.ExtensionContext dependency optional.

What changes have you made?

  • The VSCE Toolroom open-source collective has adopted the Textmate language service project!
  • Redesigned the logo, inspired by the V8 engine and the Textmate osteopermum flower.
  • Added support for tokenization and Language providers from built-in grammars as well as service-only grammars.
  • Marked TextmateLanguageService~context parameter as optional in the API types.
  • Marked the API from 1.0.0 as compatible with 1.55.0, not 1.51.0.
  • Provided community resolution to getLanguageConfiguration() API method is missing microsoft/vscode#109919 & getTokenInformationAtPosition API causes too much traffic and blocks the renderer process microsoft/vscode#99356.
  • Implemented API methods in an api namespace for developer-friendly logic:
    • Add getTokenInformationAtPosition method for fast positional token polyfill: vscode.TokenInformation.
    • Add getScopeInformationAtPosition method to get Textmate token data: TextmateToken.
    • Add getScopeRangeAtPosition method to get token range: vscode.Range.
    • Add getLanguageConfiguration method for language configuration: LanguageDefinition.
    • Add getGrammarConfiguration method to get language grammar wiring: GrammarLanguageDefinition.
    • Add getContributorExtension method to get extension source of language ID: vscode.Extension.
  • Linted the Textmate scope parser correctly & automatically in the test pipeline.
  • Added getOniguruma to API utilities, a browser-ready non-streaming build of vscode-oniguruma.

What tests have you completed?

  • Tested this in Visual Studio Code v1.82.0.
  • Tested this in Visual Studio Code Insiders v1.83.0.
  • Tested this for GitHub Codespaces v1.83.0.
  • Tested this in VSCodium v1.82.0.

Anything else worth mentioning?

We have skipped some tests for textmate-languageservice-contributes (service-only grammar wirings).
It would behoove us to investigate enabling these tests using a fallback plaintext tokenization.
Collateral: #45

zm-cttae and others added 30 commits April 1, 2023 13:22
Wire up README with 2023 V-engine logo.
Also move advisory to the Installation section.
This targets `textmate-languageservice-contributes` fake manifest key.
@zm-cttae zm-cttae merged commit cd507d1 into main Sep 8, 2023
1 check failed
@zm-cttae zm-cttae removed their assignment Sep 8, 2023
@zm-cttae zm-cttae deleted the release-candidate/2.0.0 branch September 9, 2023 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant