takeupT
As in "take up carpentry". The "record create" endpoint.
The development CRUD... All the TURDs... Do them one. last. time. Squeeze out a bunch of world record, Randy Marsh sized CRAPs. Do them well. Tim Bushell
eliobones provides reusable endpoints for manipulating a "thing"s data, according to the design_pattern.
Its core ribs are 10 endpoints. They enclose the beating heart of elioWay projects. You will engage them a lot!
Four elioEngage operations - for working with the top level object - the engaged "thing":
takeupT
As in "take up carpentry". The "record create" endpoint.
updateT
The "record update" endpoint.
readT
The "record get" endpoint.
destroyT
The "record delete" endpoint.
Four elioList endpoints:
listT
The "list all relateds record" endpoint.
unlistT
The "record remove from list" endpoint.
takeonT
The "record create and add to list" endpoint.
enlistT
The "record add to list" endpoint.
Two elioSchema endpoints:
pingT
An endpoint for checking the availability of endpoints.
schemaT
An endpoint for getting metadata, or for getting a new blank record.
These are called internally by the endpoints, but could be called independently for other purposes:
engageT
An endpoint which is a light wrapper for opening.
authT
An endpoint for checking the user is Permitted to call each endpoint.
permitT
Called by authT
. An endpoint for checking the user is Permitted to proceed.
As long as the endpoint acts upon a complete thing
, with or without a list, and returns the payload correctly formatted, it is an elioBone.
Here are, for instance, three elioOptimize endpoints, the very least we could do. We expect you'll need more. You'll have to write those yourself and share them. We'll share any we write here as well. But for now... We feel it's the least we owe.
inviteT
Create a token and corresponding Permit to inviteT
others to view/edit your thing.
optimizeT
Report on the combined Action.actionStatus
of listed things.
undoT
Reverse data changes by going back a certain number of steps. Write me! It will be fun.