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
[feat] Updated jsdoctypeparser package. #196
[feat] Updated jsdoctypeparser package. #196
Conversation
Awesome! Take your time, I can't issue an update yet anyway. It turns out I don't currently have npm publish rights for the dox package, it got lost when I had them rename my account a few months back. I'm waiting to hear back from support on the matter. |
any updates regarding this PR status of being a Draft and the npm publish rights? |
@hasezoey Publish rights have been worked out, that's how I published 0.9.1 |
d6f471a
to
85070b0
Compare
85070b0
to
1c7d017
Compare
Sorry about the severe delay in continuing work for this PR; life just got away from me. I did make some progress in fixing the remaining issues. I also removed all of the commits related to using Jest as the test running, as I'm trying to keep this PR as simple as possible. I can add it back in another PR if you'd like. I have one final issue that I'm bumping up against in the
This returns the following error:
I've been digging through JSDocs documentation, and I can't find any reference to returning an object like this, and from what I can grok by the syntax I would assume it would return an object rather than an array. Again, sorry for the delay. |
@neogeek I think the issue is simply that the old jsdoctypeparser always returned record types in an array, so that's what the test checked for. |
I figured that was the case, but I was unsure if I should just wrap the types. I pushed a commit that wraps the object in an array and all of the tests pass! |
I did unfortunately find an error when running a custom suite of tests. It's an issue related to the types where an object will get converted to |
I pushed a fix for the issue I mentioned above. I'm going to look into adding tests to cover this scenario. |
Added a test to cover that scenario! I'll keep testing in my own environment, but I think this PR should be good to go. |
@neogeek are we calling it done now? All tests passing, are you comfortable with me merging it? |
Fuggit, yolo |
I am. I would still like to create a separate PR to improve the testing suite to cover more that what it covers now, if you are ok with that. Finding something the tests do not cover made me a bit nervous. |
Please do! More tests is good |
Will do! |
I'll have a new release out tonight. 1.0.0, here we come! |
We have 1.0.0! https://github.com/tj/dox/releases/tag/v1.0.0 |
This PR is still very much a work in progress.
jsdoctypeparser
package was updated. I can remove them before taking the PR out of draft mode.jsdoctypeparser
package and usage.Error:
SyntaxError: Expected [ \t], [\n], [\r], or end of input but "n" found.
The tests currently fail, but I feel like I'm close to fixing the remaining issues.