In Node (and React-native) the WebSocket constructor can take additional parameter which can set the HTTP request options for the initial request. This can be used to set headers etc.

https://github.com/theturtle32/WebSocket-Node/blob/master/docs/W3CWebSocket.md#constructor
https://github.com/facebook/react-native/blob/29fb2a8e90fa3811f9485d4b89d9dbcfffea93a6/Libraries/WebSocket/WebSocket.js#L

There's an hint of an Attachments section in the response.md docs at this link https://github.com/coast-framework/coast/blob/571d3ec9487741123331538d8e725315e011f154/docs/response.md#user-content-attachments, but the actual section is missing.

Is this because the implementation is missing or just a lack of docs about it?

P.S.: in the meantime it would be nice to know how to deal with att

Just make this legal for top-level fiddles, it's simpler. Right now a :db/id link encodes a long into the URL, not an entity ref

add as a gitbook plugin

ring-defaults' wrap-defaults adds the ring.middleware.content-type/wrap-content-type middleware by default (see https://github.com/ring-clojure/ring-defaults/blob/master/src/ring/middleware/defaults.clj#L27 and further occurences of :content-types)
Muuntaja's muuntaja.middleware/wrap-format will silently not do anything when ring's content-type middleware is also present.

Is it possibl

Hi,

Working with graphqlize-demo I did not found how to enable logging for the generated SQL.
It would be great if this was available in a documentation section.

I'm thinking of something like the logging found in spring apps which I am familiar with: https://www.baeldung.com/spring-boot-testing-log-level

I should be able to do something like

logging.level.honeyeql=DEBUG 

In status-react we are using similar build configs in clj-rn.conf.edn and build.clj. The first one seem to be used for the watch task and the second one for compile and test. We should unify both into clj-rn.conf.edn as it seems to be the one used by clj-rn

• streamline getting started - choose a methodology where a bundled sim is not used
• consolidate over sample-petstore and petstore-demo (they seem to be almost the same thing barring a sim extension)
• add versioning to documentation