This change adds a single page application front-end to GARM. It uses a generated REST client, built from the swagger definitions, the websocket interface for live updates of entities and eager loading of everything except runners, as users may have many runners and we don't want to load hundreds of runners in memory. Proper pagination should be implemented in the API, in future commits, to avoid loading lots of elements for no reason. Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com> |
||
|---|---|---|
| .. | ||
| .editorconfig | ||
| .gitignore | ||
| .golangci.yml | ||
| CODE_OF_CONDUCT.md | ||
| errors.go | ||
| LICENSE | ||
| pointer.go | ||
| README.md | ||
gojsonpointer

An implementation of JSON Pointer - Go language
Status
Completed YES
Tested YES
References
http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-07
Note
The 4.Evaluation part of the previous reference, starting with 'If the currently referenced value is a JSON array, the reference token MUST contain either...' is not implemented.