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
A good way to reproduce this is to remove the cd() I re-added in f6a5f19 and run the tests. Every one of the test_build_ts tests will fail.
The computation of path in the analyzer's make_meta() doesn't make any sense to me. Especially since typedoc could be passed multiple unrelated directories in a single invocation (if js_source_path was a list), we should be computing the root_for_relative_js_paths-relative paths of things based on the originalName properties of the typedoc --json output, which are absolute paths.
More broadly, the entirety of the TypeScript analyzer needs to be re-examined and re-expressed in terms of an IR (#120). It also needs to have its tests replaced. They currently compare the whole output of the analyzer on 10 different TS files. The resulting redundant assertions magnify brittleness upon any code change and obscure which parts of the comparison are important.
See #77, #103, #109, and #143 for bugs that will be easier to fix once this is done.
The text was updated successfully, but these errors were encountered:
…faces (mozilla#148)
When rendering a jsfunction, jsclass, or jsinterface, if there are type params
include them. Like:
```js
function f<S, T>(x, y)
```
I also removed the parens from classes and interfaces because they look weird.
We had to add an extra docutils node for js-type-params because the normal type
params docutils node uses square brackets not angle brackets.
A good way to reproduce this is to remove the
cd()
I re-added in f6a5f19 and run the tests. Every one of the test_build_ts tests will fail.The computation of
path
in the analyzer'smake_meta()
doesn't make any sense to me. Especially sincetypedoc
could be passed multiple unrelated directories in a single invocation (ifjs_source_path
was a list), we should be computing the root_for_relative_js_paths-relative paths of things based on theoriginalName
properties of thetypedoc --json
output, which are absolute paths.More broadly, the entirety of the TypeScript analyzer needs to be re-examined and re-expressed in terms of an IR (#120). It also needs to have its tests replaced. They currently compare the whole output of the analyzer on 10 different TS files. The resulting redundant assertions magnify brittleness upon any code change and obscure which parts of the comparison are important.
See #77, #103, #109, and #143 for bugs that will be easier to fix once this is done.
The text was updated successfully, but these errors were encountered: