-
See how `eslint-plugin-jsdoc` `README.md` document is generated:
- https://github.com/gajus/eslint-plugin-jsdoc/tree/master/.README
- https://github.com/gajus/eslint-plugin-jsdoc/blob/dca8ddc83aa10290…
gajus updated
8 years ago
-
# Suggestion
## 🔍 Search Terms
`@implements` `jsdoc` `import` `export`
## ✅ Viability Checklist
My suggestion meets these guidelines:
* [x] This wouldn't be a breaking change in existin…
-
**Update**: see updated description [below](https://github.com/eslint/eslint/issues/14745#issuecomment-888205829)
**The version of ESLint you are using.**
7.29.0
**The problem you want to sol…
-
### Describe the bug
When I try to use vite-plugin-dts to build the .d.ts declaration file of the lib.
In the final result, my props and emits comments are lost.
In the Demo, you can intuitively …
-
I am using `{*}` for the "any" type in my JSDoc which I think is the standard usage. This is used in examples on these pages:
- https://jsdoc.app/tags-type
- https://www.typescriptlang.org/docs/hand…
-
## The devDependency [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) was updated from `15.8.1` to `15.8.2`.
🚨 [View failing branch](https://github.com/so5/get-ami/compare/master.…
-
## The dependency [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) was updated from `3.14.1` to `3.15.0`.
🚨 [View failing branch](https://github.com/davidosomething/16.davidosomet…
-
I'm tinkering around to see if this is possible but would love to avoid going down a rabbit hole if not likely to work.
https://github.com/wvbe/experimental-jsdoc-to-tsdoc-tool
I've been using …
-
Related #21238, #17271.
### 1. Should we allow JSDoc type notation?
JSDoc and TypeScript type notations are different. They can create confusion. For example:
* `[string]` means an optional s…
-
As part of the build process, [CesiumJS generates TypeScript definitions based off our jsdoc comments](https://github.com/CesiumGS/cesium/pull/8878).
While we're generally pretty meticulous about h…
ggetz updated
4 weeks ago