Manuel Spigolon

In general, I think the fastify website tech stack is out of date and need an upgrade. I think the "must have" features are: - Fastify's version dropdown to see...

> Regarding versioning: I also agree that we should drop the patch (and I think minor) versions of the docs. I propose having 1.x, 2.x, 3.x, and next (or similar)...

> Where do we go from there? ToC for vX.Y.Z ? > > Maybe at that point it could make more sense to just print the entire ToC for vX.Y.Z...

I agree to unify the docs and for CJS or ESM I saw a simple switch that shows the syntax chosen by the user (I cant remember which module) I...

Personally, I think `app` is misleading because it seems the main root application. This is true only when the user uses the `fastify-plugin` and not when a new context is...

I don't know exactly the problem here for oas. In fastify-swagger all the schemas added with `addSchema` are not given to the `swagger-ui`, for this reason it is unable to...

I'll try to explain what is happening - v2: this `vacation: 'sharedAddress#'`, at runtime, become `vacation: { a json }`. The string is replaced with the right object. NB: v2...

I was thinking that a command `setup` could be useful to add to a GitHub repo some label (configured) in order to facilitate the process Relates to #1

The use case I had in mind was: I have many repo (50 plugins) and I would like to add `semver-*` labels to them in order to have all the...

Backing back to the template system for the release message. The pattern could be: `1 title => 1 semver version corresponding => array of labels` if the PR's labels don't...