3forges / pesto-api

The Pesto REST API
0 stars 0 forks source link

Next TODO: how to resume #1

Open Jean-Baptiste-Lasselle opened 1 year ago

Jean-Baptiste-Lasselle commented 1 year ago
# --- 
#  + - + NEW VERY IMPORTANT :
#  THE NEXT THING I IMPLEMENT IS : 
#    -> PESTO PROJECT FEATURE : it has no foreign key it is a root object of the model
#    -> PESTO CONTENT FEATURE : it has 2 foreign keys, one [project_id] ("FK" to 'PestoProject' entity), and one [type_id] ("FK" to 'PestoContentType' entity) 
#        +-> FIND 'PestoContent' BY 'PestoProject' 
#        +-> FIND 'PestoContent' BY 'PestoContentType'
# 
# --- 
# Ok now we are going to list all 
# [Pesto Content Types] for a given [Project ID]:
# --- 
# 
export PESTO_PRJ_ID="rubbishprjid3modified"
curl -iv -X GET -H 'Accept: application/json' "http://localhost:3000/pesto-content-type/project/${PESTO_PRJ_ID}" | tail -n 1 | jq . 
Jean-Baptiste-Lasselle commented 1 year ago

NEXT TODO: OK HERE I NEED TO BE ABLE TO ADD A PESTO CONTENT TYPE INTO A PROJECT BY PROJECT NAME NOT BY PROJECT ID

Jean-Baptiste-Lasselle commented 1 year ago

I implemented all, now i only need to add 2 rules :

Jean-Baptiste-Lasselle commented 1 year ago
  • I have my PestoProject Endpoint which works,

NEXT TODO: OK HERE I NEED TO BE ABLE TO ADD A PESTO CONTENT TYPE INTO A PROJECT BY PROJECT NAME NOT BY PROJECT ID

This one i do not implement it yet, its not interesting, the GET requests anyway always pull mongo db _id fields, that will be enough to provide a @pesto/api-client package to be able to hit the pesto api easily

Jean-Baptiste-Lasselle commented 1 year ago

https://github.com/3forges/poc-frontmatter-schema/issues/1 gives me details about the next and last task:

Choose a frontmatter management strategy