You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each section contains error diagnostics that arise when checking the code block above. and it's not all aesthetic these code blocks are tested against the checker with a custom testing crate
The aim of this document is to break down the features into parts so
we know what is currently implemented
we know what is not currently implemented (via to_implement.md)
Find regressions in behaviour after fixing or adding new features (newer features breaking older checker features)
Ezno will hopefully be useful on new projects with little dependencies at around ~250 tests passing. At the around the 400-500 mark it might be ready for existing projects.
I need your help in writing more
Write them in staging, merge them either into to_implement.md if it doesn't work or if they do, then specification.md
Optionally write corresponding issues for failing specification tests
Check existing specification.md for improvements to coverage or invalid cases
Tip
Maybe you have a favourite JS feature or something you think is great that TSC does great at checking and isn't currently covered. Then it would be great to add it!
this is a general issue, that can relate to many pull requests
The text was updated successfully, but these errors were encountered:
Will come back to this add more guidance in a few weeks. Just realised I should go into more detail about the difference to Ezno and TSC errors/diagnostics. I haven't published the document which shows a comparison yet...
If you haven't seen already Ezno has a document that outlines all its current checking capabilities!
Each section contains error diagnostics that arise when checking the code block above. and it's not all aesthetic these code blocks are tested against the checker with a custom testing crate
The aim of this document is to break down the features into parts so
to_implement.md
)At the time of writing. 129 tests currently pass
Important
Ezno will hopefully be useful on new projects with little dependencies at around ~250 tests passing. At the around the 400-500 mark it might be ready for existing projects.
I need your help in writing more
staging
, merge them either intoto_implement.md
if it doesn't work or if they do, thenspecification.md
specification.md
for improvements to coverage or invalid casesTip
Maybe you have a favourite JS feature or something you think is great that TSC does great at checking and isn't currently covered. Then it would be great to add it!
this is a general issue, that can relate to many pull requests
The text was updated successfully, but these errors were encountered: