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
There is already a symbol_tester.rs, however, I think there are some flaws:
it could not distinguish different symbol with same name.
functionfoo(){constfoo=123;}
For this example, I think there is no way to assert that there are 2 symbols called "foo" and assert the status of inner "foo" symbol
it checkes implementation details. This might be good for some situations, but always arguable
Not pretty easy to use.
So, I suggest to add another tester, which refer typescript's design:
For one input file, typescirpt will generate 4 output file
js
type
symbols
errors.txt
I believe there is already a js files output tester. So it's kind of natural to have another one for symbol.
In the symbol baseline file, for each appeared identifier, it's needed to record its the symbol, which could be done thorugh the span of declaration symbol.
There is already a symbol_tester.rs, however, I think there are some flaws:
For this example, I think there is no way to assert that there are 2 symbols called "foo" and assert the status of inner "foo" symbol
So, I suggest to add another tester, which refer typescript's design:
For one input file, typescirpt will generate 4 output file
I believe there is already a js files output tester. So it's kind of natural to have another one for symbol.
In the symbol baseline file, for each appeared identifier, it's needed to record its the symbol, which could be done thorugh the span of declaration symbol.
this is an example from typescript repo:
The text was updated successfully, but these errors were encountered: