* Minor update to gharial list call
* Updated documentation for graph creation API
* Updated graph get documentation
* Added a section for Query Parameters in Graph Create
* Improved gharial drop documentation
* Added ReturnBodies for graph creation results
* Added the response object description to graph list
* Minor typo
* Added response bodies to graph get documentation.
* Added Response Body documentation on Graph grop
* Added HTTP documentation for add graph vertex collection
* Added dots to finish one-line API description sentences.
* ReplyBodyNames have to be globally unique 😢
* Documented ResponseBodies for vertex-collection-add
* Documented ResponseBodies for vertex-collection-remove
* Added result bodies for create vertex in graph documentation
* started to extract structure in separate file
* Fixed orphan structure reference
* Reuse the same documentation structore in all Graph APIs
* Documented list edge collections in GraphAPI
* Unified vertex representation
* Documented edge definition creation API
* Documented modification of edge definition
* fix support for external structure definitions
* Unified edge definition struct
* Added documentation code for vertex CRUD in Gharial
* Removed unused struct in GraphRestDocu
* Added documentation for edge CRUD in gharial. Fixed wording in vertex CRUD part
* Added missing dots at end of sentences
* MOre dots at end of sentences
* Removed empty lines
* Fixed missing edge_definition remove documentation
* Fixed a typo
Next steps after DC2DC and Cluster doc improvements:
- We refactor replication sections and make more intuitive separation between Master/Slave and the new Active Failover in 3.3
- We create corresponding sections for Master/Slave and Active Failover in the Administration and Deployment chapters, as well as in the Scalability chapter, where these "modes" are introduced
- We touch and improve the "Architecture" chapter as well, where some architecture info have to be placed
- We reorg the TOC having in more "logical" order:
-- Deployment
-- Administration
-- Security
-- Monitoring
-- Troubleshooting
- We adds parts in the TOC
- We add toc per pages, using page-toc plugin
- We also put close together "Scalability" and "Architecture" chapters, preliminary steps of further improvements / aggregation
- We improve swagger
Internal Ref:
- https://github.com/arangodb/planning/issues/1692
- https://github.com/arangodb/planning/issues/1655
- https://github.com/arangodb/planning/issues/1858
- https://github.com/arangodb/planning/issues/973 (partial fix)
- https://github.com/arangodb/planning/issues/1498 (partial fix)
* Improve Foxx cluster resilience
Fixes#2083Fixes#2384Fixes#2408
Addresses #1892
* Port old Foxx API
* Implement single-file services
* Add console.errorStack/warnStack/infoStack helpers
* Simplify serviceInfo validation
* Extract github/upload logic into Aardvark and old FM API
* Move generator logic into Aardvark
* Move zip/js buffer logic into FM core
* Add Foxxmanager tests
* Send empty response when no README
* Disambiguate script arg format
Historically we allow passing an array of positional arguments or an arbitrary first argument.
This is surprising behaviour, so we should just always treat the value as a first argument.
* Rebuild bundle in development mode
* Nicer HTTP docs formatting
* Create Foxx HTTP docs
* Simplify service upload handling
* Remove inline swagger docs
* Implement public download route
* Consistency
* Rebuild aardvark
* Move bundle route into /_api/foxx/_local
* Rebuild Swagger API docs
* Add changes to CHANGELOG
* More docs