Upgrade all core fastify plugins to v3

Upgrade info

There are a number of breaking changes which can be found here:
https://github.com/fastify/fastify/blob/899382d682846b07bb706346a1a3f1165d87e369/docs/Migration-Guide-V3.md

Ensure you use latest version of fastify-plugin to get correct types:

While upgrading a plugin ensure that:

• All warnings are fixed (e.g. request.req ->

Description

The documentation on Error Handling indicates there should be a stack trace, but stack traces are no longer returned.

Steps to Reproduce the Problem

1. buffalo new coke
2. cd coke
3. buffalo dev &
4. curl -H 'Content-Type: application/json' 'http://localhost:3000/does_not_exist'

Expected Behavior

trace and

I would like to see a list of partners, open source projects or big companies who uses ninja as a vote of confidence for choosing ninja as your next project's foundation.

I'm on a pet project that requires a performant CoAP webserver. Since none exist I was considering using libcoap and find a frontend for doing the routing/middleware. Silicon looks to fit the build! How hard would it be to add libcoap as a Silicon backend? Are there any docs or guidance?

Thanks!

As of #424 we can match on multiple Accept types. The examples haven't yet been updated for this behavior yet, however.

Describe the solution you'd like
I would love it if Genie.jl auto-generated a swagger documentation page like plumber does for the R ecosystem. (Or does it already, sorry if I just missed that.)

Describe alternatives you've considered
Swagger.jl, but all the Java makes it seem like a tough dependency.

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.

What is missing at the moment:

• age
• country
• week day
• ip address
• colour
• Lorem Lipsum - for general text, e.g. description etc
• work position
• salutation

Please add anything you can think of in the comment below

Hi Daniel,

A few more issues with the online tutorial (not trying to be picky here, but these are the issues I encountered):

In https://github.com/cutelyst/cutelyst/wiki/Tutorial_03_MoreCutelystBasics#register-a-cutelyst-view :

target_link_libraries(Hello
    ...
    Cutelyst::View::Grantlee # Add this line
    ...
}

should be:

target_link_libraries(MyApp
    ..

The tutorial suggests editing the cabal file to add dependencies for use with stack. My understanding is that the dependencies are to be added in the package.yaml file and not the cabal file for use with stack. Is this what was intended? I just confused a newcomer with contradictory advice to the contents of the tutorial.

Ref: https://docs.haskellstack.org/en/stable/GUIDE/#files-in-helloworld

We should be able to set stateless / stateful on each auth scheme independently, because an app may have 2 or more auth schemes, for example jwt/generic with stateless and form with stateful.

Current solution from @jeevatkm: achieve the stateless via interceptor (https://docs.aahframework.org/interceptors.html) - define action or controller level Finally interceptor and then call `ctx.Session

Assuming that luminus-framework/luminus-template#452 merges, we'll have at least some automated tests that could be used to pick up on regressions.

I think we should integrate w/ Travis CI (Travis + Clojure docs here) or similar, & then (later, ongoing) look at adding to our test suite for increased confidence.

Users should not be doing password hashing, registration stuff etc. by hand. Node.js already has really good support in the form of passport.js. The equivalents in other frameworks are Devise and Django-allauth.

It could save some confusion if the control panel got a mention near the beginning of https://github.com/SeasideSt/Seaside - somewhere near the 'launch the welcome page' section.

See https://kapeli.com/docsets. This pkg might provide a quick means to generate the docset: https://pypi.org/project/sphinxcontrib-dashbuilder/