Joël Gähwiler
Joël Gähwiler
If a client receives a message that is bigger than its receive buffer if will crash and return the error "LWMQTT_BUFFER_TOO_SHORT". For this library the better approach would be to...
To aid with debugging, an error/event reporting interface should be added. This should be configurable as the `Serial` port might be used for something else. A rough sketch: ```c++ void...
There have been various requests for adding a chunked reading and writing API to process messages that are larger than the configured buffer size. This issue is to track the...
Currently only the model containing the reference offers the JSON-API relationship mutation APIs. But, the standard also allows mutation from the has-one and has-many relationship.
The `?included=` parameter is currently ignored. The controller should provide a mechanism to enable resource inclusion per related resource.
The following query operators are missing. - [x] `$not` - [ ] Regex - [x] `$in` - [ ] Regex - [ ] `$expr` - [x] `$jsonSchema` - [ ]...
The following update operators and modifiers are missing: - [ ] `$` - [ ] `$addToSet` - [ ] `$each` - [x] `$pop` - [ ] `$pull` - [x] `$push`...
The following projection operators are missing: - [ ] `$` - [ ] `$elemMatch` - [ ] (`$meta`)
As only two of many errors are exported, they will be removed with #261 to be concise. This issue should track the discussion about how errors should be exported again...
Hi, I found a small inconsistency while working on [fire](https://github.com/256dpi/fire). Let's say I have a model that exposes a HasMany relationship that is not loaded: ``` go // Post jsonapi.Reference{...