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

Volar-ized Glint Roadmap #728

Closed
2 of 12 tasks
machty opened this issue Jun 20, 2024 · 2 comments
Closed
2 of 12 tasks

Volar-ized Glint Roadmap #728

machty opened this issue Jun 20, 2024 · 2 comments

Comments

@machty
Copy link
Contributor

machty commented Jun 20, 2024

Overview

This roadmap absorbs the contents of the now-closed Language Tooling RFC.

Now that the initial Volar Refactor PR has been merged, there a number of next steps to pursue before Glint 2.0 is ready for primetime.

Roadmap

  • Fix test suite, all green tests, via test.skip() (and add to this issue for any remaining feature TODOs)

  • - [x] Fix glint --build --clean specs (broken since Volar -- cleans everything but .gts file outputs). Johnson thinks it can be supported, needs upstream fix.

  • Support for .gjs (and passing tests)

  • Support for .hbs and companion files

  • Reinstate disabled CI:

    • eslint
    • windows (blocked on volar 2.4.0 breaking stuff, discussion here)
    • type-tests
    • test-floating-deps
    • test-ts-nightly
  • Figure out how to resolve conflicts/overlapping with vsc-ember-syntax Transfer to ember-tooling lifeart/vsc-ember-syntax#72

    • I need to review how/why I inlined portions of that addon into this branch; I believe it's because otherwise Glint/Volar can't determine a language ID for .gts files
  • get all {{ @glint-expect-error }} and related directives working

  • constrain data objects on nested embedded codes https://discord.com/channels/1192759067815464990/1252021970443440128/1252298644695158874

@machty
Copy link
Contributor Author

machty commented Jul 3, 2024

CI is green; now to unskip and fix a number of specs where the underlying behavior is actually correct, but the test is broken.

@machty
Copy link
Contributor Author

machty commented Sep 25, 2024

Closing this in favor of a soon to be published GH project. All of the items contained within have been extracted/converted into GH issues.

@machty machty closed this as completed Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant