JSDoc Reviews

Jsonnet Reviews

JSDoc mentions (57)

• Express Setup: Simple & Scalable

  In our JSDoc comments we describe our endpoints to using a set of tags, you can look at the different tags and what they do over on JSDoc's website but here's what we've used and why. - Source: dev.to / over 1 year ago

• Connecting the Custom Elements Manifest to Figma Code Connect

  Most analysers that generate a Custom Elements Manifest operate by extending JSDoc comments. In our case, we'll need to add a @figma tag to our component comments so that we can tie the two together. The URL provided here can be found by selecting the main component in Figma and copying the link. Both the file name and node-id are key pieces of information that we'll need to query the Figma API later. - Source: dev.to / 9 months ago

• Ask HN: Abandoned/dead projects you think died before their time and why?

  If your IDE supports JSDoc, then TS isn't needed for basic type constraints. https://jsdoc.app/. - Source: Hacker News / 9 months ago

• Documenting Web Components With Storybook

  One of the best tools available in Web Component development is the Custom Elements Manifest. It's a JSON representation of all your available components, covering all the attributes, methods, slots and events they support, powered by your JSDoc comments and TypeScript types. You can customize the manifest generation through plugins to support custom JSDoc comments, allowing you to power more pieces of your... - Source: dev.to / over 1 year ago

• Just Say No to JavaScript

  I've seen several ways of annotating Javascript that IDEs seem to understand. They usually involve using comments before fields, classes, or functions. The most compliant one seems to be using [JSDoc](https://jsdoc.app/). JSDoc is mostly intended for generating documentation. However, the Typescript compiler can validate types (and can even interoperate with Typescript definitions), if you configure it as such. In... - Source: Hacker News / over 1 year ago

Jsonnet mentions (38)

• YAMLpp is dynamic,self-generating YAML

  OK, what we can do now? Use a preprocessing language guaranteed to produce valid syntax, like Jsonnet for json? That wil work, for sure. However, you have now a friction problem: it's new file format that requires implementing its own toolchain (Jsonnet is not json, so editor add-ons, parsers, interpreters, libraries, etc.) and you will need to drive the team through the learning curve of a language with its own... - Source: dev.to / 8 months ago

• Levels of Configuration Languages

  Https://jsonnet.org/ I never heard of this before. This seems like the JSON I wish I really had. Of course at some point you could just use JavaScript. - Source: Hacker News / over 1 year ago

• Standard ML idiosyncrasies

  I've been reading the book Modern Compiler Implementation in ML lately. It's been helpful to brush up on some concepts while developing Tsonnet (my typed-aspiring Jsonnet flavor) and I hope to learn a ton more. However, I'm growing dissatisfied with some details -- not specifically the book, but the choice of the development environment. - Source: dev.to / over 1 year ago

• Tsonnet, a humble beginning

  For the past 2 years, I've been working extensively with Jsonnet, a configuration language that augments JSON and helps eliminate repetition in our config files. It has its limits (many by design), which keeps the language simple to use. But there's one thing that keeps nagging at me when I'm deep in the code: what's the shape of the input or output of this function? And wouldn't it be great if we could type... - Source: dev.to / over 1 year ago

• Refactor Terraform Resource Names By One Command

  Jsonnet: Use --jsonnet (-j) for advanced, programmatically controlled renaming logic. - Source: dev.to / over 1 year ago