https://github.com/nerdfiles/api.senecajs.rest_api
🌠Microservices-based REST API for clients following HATEOAS.
https://github.com/nerdfiles/api.senecajs.rest_api
expressjs hypermedia-api rest seneca-entity seneca-web-adapter-connect senecajs
Last synced: about 1 year ago
JSON representation
🌠Microservices-based REST API for clients following HATEOAS.
- Host: GitHub
- URL: https://github.com/nerdfiles/api.senecajs.rest_api
- Owner: nerdfiles
- Created: 2017-05-27T17:46:37.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2022-12-30T19:54:15.000Z (over 3 years ago)
- Last Synced: 2024-04-15T07:42:43.767Z (about 2 years ago)
- Topics: expressjs, hypermedia-api, rest, seneca-entity, seneca-web-adapter-connect, senecajs
- Language: JavaScript
- Homepage:
- Size: 2.67 MB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 20
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# API.SenecaJS.REST_API
$ npm i && npm i jq -g
$ bin/program -h
$ bin/program service
Elsewhere:
$ source scripts/resty.sh
$ resty.set 'http://localhost:8081/api'
$ GET /noop | jq '.'
We should see a broke-ass HAL-ish JSON output:
```json
{
"_links": {
"self": {
"href": "/noop"
},
"test": {
"href": "/noop/test"
}
},
"name": "noop",
"data": "yellowfish"
}
```
## wut?
Do [*actions*][action] from or against *models* as *role*-based *commands* which
will result in *statuses*. Configure *contracts* and *components* to taste,
bearing in mind...
If the engine of application state (and hence the API) is not being driven by
hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there
some broken manual somewhere that needs to be fixed?
Roy Fielding
## Updates
Coming soon...
[action]: https://schema.org/Action