-
Notifications
You must be signed in to change notification settings - Fork 0
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
JSDoc can bug the plugin #2
Comments
I also don't know which versions you would need to check that soooo... $> yarn list | grep babel
├─ [email protected]
├─ [email protected]
│ ├─ babel-code-frame@^6.26.0
│ ├─ babel-generator@^6.26.0
│ ├─ babel-helpers@^6.24.1
│ ├─ babel-messages@^6.23.0
│ ├─ babel-register@^6.26.0
│ ├─ babel-runtime@^6.26.0
│ ├─ babel-template@^6.26.0
│ ├─ babel-traverse@^6.26.0
│ ├─ babel-types@^6.26.0
├─ [email protected]
│ ├─ babel-messages@^6.23.0
│ ├─ babel-runtime@^6.26.0
│ ├─ babel-types@^6.26.0
├─ [email protected]
│ ├─ babel-runtime@^6.22.0
│ └─ babel-template@^6.24.1
├─ [email protected]
│ ├─ babel-core@^6.0.0
│ ├─ babel-plugin-istanbul@^4.0.0
│ └─ babel-preset-jest@^20.0.3
├─ [email protected]
│ └─ babel-runtime@^6.22.0
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
│ └─ babel-plugin-jest-hoist@^20.0.3
├─ [email protected]
│ ├─ babel-core@^6.26.0
│ ├─ babel-runtime@^6.26.0
├─ [email protected]
├─ [email protected]
│ ├─ babel-runtime@^6.26.0
│ ├─ babel-traverse@^6.26.0
│ ├─ babel-types@^6.26.0
├─ [email protected]
│ ├─ babel-code-frame@^6.26.0
│ ├─ babel-messages@^6.23.0
│ ├─ babel-runtime@^6.26.0
│ ├─ babel-types@^6.26.0
├─ [email protected]
│ ├─ babel-runtime@^6.26.0
│ └─ babel-runtime@^6.18.0
│ ├─ babel-code-frame@^6.22.0
│ ├─ babel-generator@^6.18.0
│ ├─ babel-template@^6.16.0
│ ├─ babel-traverse@^6.18.0
│ ├─ babel-types@^6.18.0
│ ├─ babel-core@^6.0.0
│ ├─ babel-jest@^20.0.3
│ ├─ babel-plugin-istanbul@^4.0.0
│ │ ├─ babel-code-frame@^6.16.0
│ ├─ babel-runtime@^6.23.0
│ │ ├─ babel-code-frame@^6.16.0
│ │ ├─ babel-code-frame@^6.16.0 |
Turns out, it relates to the JSDoc, this exports the function as expected: 'use strict'
// Using false will remove the entry from the object and will ease the roles retrieval
const Overrides = {
zob : true,
}
/**
* Filter rights according to their Boolean value
* @param {Object} rights An object with rights to filter on
* @return {Array} The list of rights available to this user
*/
// @test-export
function format(rights) {
console.log('whatever')
}
module.exports = {} The only thing I changed is the return type that is an |
Thanks for the report. I don't think it's a JSDoc issue. I managed to reproduce without the JSDoc comment. It seems that since babylon 6.17.2, comments are sometimes attached to the previous statement (as trailing comments), if it doesn't end with a semicolon. I published a new version, please try out :) |
Will do on monday :) |
This code doesn't expose the marked as exposed function
But this one does
The diff between the two is the following:
I tried looking at the src but I must admit I'm no good at reCAST 😆
The text was updated successfully, but these errors were encountered: