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

Getters and setters are missing jsdoc types in 0.2.81 (not 0.2.80) #2947

Closed
dsherret opened this issue Jun 16, 2022 · 2 comments
Closed

Getters and setters are missing jsdoc types in 0.2.81 (not 0.2.80) #2947

dsherret opened this issue Jun 16, 2022 · 2 comments
Labels

Comments

@dsherret
Copy link
Contributor

dsherret commented Jun 16, 2022

Describe the Bug

In the latest 0.2.81 the .js file is missing jsdoc types on getters and setters. This is because in #2909 they were set to None: https://github.com/rustwasm/wasm-bindgen/pull/2909/files#diff-072222e984a549efeebf98f26d0c59a69d88abe246db7e0958654fc32471313eR2531

Steps to Reproduce

Sorry, I do not have time right now to offer a simple reproduction, but I have pointed out the cause in the code above. Also a fix can be seen here, which is a revert of the above: 387e821 -- but it is probably not a real fix since this was done for some reason in #2909

Expected Behavior

Getters and setters should still have jsdoc comment types when not using TypeScript.

Actual Behavior

The types are missing in 0.2.81

cc @Hywan

@dsherret dsherret added the bug label Jun 16, 2022
@dsherret dsherret changed the title TypeScript getters and setters are missing jsdoc types in 0.2.81 (not 0.2.80) Getters and setters are missing jsdoc types in 0.2.81 (not 0.2.80) Jun 16, 2022
Hywan added a commit to Hywan/wasm-bindgen that referenced this issue Jun 20, 2022
…apters.

A bug has been raised in
rustwasm#2947, which is the
consequence of a bug introduced in
rustwasm#2909.

This patch fixes it by differentiating JS docs and TS docs
clearly. The `Context::push_setter` and `Context::push_getter` methods
now receive a `js_docs` and a `ts_docs`, which prevent any confusions.
alexcrichton pushed a commit that referenced this issue Jun 21, 2022
…apters. (#2956)

A bug has been raised in
#2947, which is the
consequence of a bug introduced in
#2909.

This patch fixes it by differentiating JS docs and TS docs
clearly. The `Context::push_setter` and `Context::push_getter` methods
now receive a `js_docs` and a `ts_docs`, which prevent any confusions.
@Hywan
Copy link
Contributor

Hywan commented Jun 22, 2022

Hello @dsherret,
Can you confirm that #2956 solves your problem? We should restore some disabled tests to ensure this behavior is totally fixed, I'll probably work on this soon.

@dsherret
Copy link
Contributor Author

@Hywan yup, it's fixed. Thanks so much for looking into it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants