GitLab

feat: support binary payload

Closes #28

See merge request !19

Resolve "Remove unused and irrelevant fields from mission plan message + add timeout"

Closes #27

See merge request !18

Resolve "MQ Topic Structure with operator appointed name"

Closes #14

See merge request !17

feat: adding url-prefix as field to swagger for nginx

See merge request !7

refactor: project content to latest

Closes #25

See merge request !13

fix: projects to project

Closes #22

See merge request !12

Resolve "Refactor test to not allow schema validation for additional properties & examples"

Closes #19

See merge request !9

Ensure example messages pass validation in javascript

See merge request !10

The destination field contains a publish topic
You don't send to the autonomy engine
You publish a message on a topic that the autonomy engine
is subscribed to.
The send/receive field is confusing.
The aim was to give clients the option to subscribe to
all messages from platforms or all messages to platforms
but it's unclear how to use this for things like the
configuration message.

I've updated the messages and schemas so that all
messages pass validation with the js validator