dociql
semver
dociql | semver | |
---|---|---|
4 | 724 | |
353 | 7,037 | |
0.8% | 0.6% | |
0.0 | 0.6 | |
about 1 month ago | 11 days ago | |
JavaScript | ||
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dociql
- Open Source: Generate GraphQL API documentation in minutes yet beautiful
-
magidoc alternatives - dociql and graphdoc
3 projects | 4 Aug 2022
Magidoc is a GraphQL documentation generator
-
Introducing SpectaQL 1.0 - an even better way to autogenerate GraphQL API documentation
SpectaQL was originally forked from a project called DociQL to add some enhancements there. And DociQL was originally forked from a project called Spectacle to make it work with GraphQL. And (finally) Spectacle was designed to work with Swagger/OpenAPI. Swagger/OpenAPI is a specification designed to help standardize the description of REST APIs with many routes, and uses JSON Schema as the way to define Data Types/Models. This means that SpectaQL had to wrestle with several layers of history and transformations; making SpectaQL's enhancements fit into the DociQL world, which in turn had to make things fit into the Spectacle/Swagger/OpenAPI world.
-
Autogenerate GraphQL API documentation with SpectaQL
There was one solution we found that was the closest to what we were looking for: DociQL. It's an open-source, node.js project that describes itself like this: "DociQL generates beautiful static HTML5 documentation from a GraphQL endpoint using the introspection query." Awesome!
semver
-
Git commit helper: add emojis to your commits
Using Conventional Commits โญ as a standard for your commit messages, makes Semantic Versioning ๐ as easy as can be, with tools like Conventional Changelog ๐ Standard Version ๐ and Semantic Release ๐ฆ๐
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseโฆ
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
What are some alternatives?
spectaql - Autogenerate static GraphQL API documentation
react-native - A framework for building native applications using React
graphql-playground - ๐ฎ GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration)
semantic-release - :package::rocket: Fully automated version management and package publishing
graphiql - GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
artwork - GraphQL Foundation artwork
changesets - ๐ฆ A way to manage your versioning and changelogs with a focus on monorepos
spectacle - Beautiful static documentation generator for OpenAPI/Swagger 2.0
helmfile - Deploy Kubernetes Helm Charts
artwork - Contains the collaborative work of the openSUSE marketing and artwork teams. Content is licensed under CC-BY-SA 3.0 (Creative Commons Attribution-ShareAlike 3.0 Unported License).
Poetry - Python packaging and dependency management made easy