You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rollthecloudinc/spearhead-canva-objects - private repo w/ pages site mapped to /public
public (map Github pages site to this folder)
panelpage
media
schema
.nojekll
design
[design id]
[submission id]
[submission id]
The contract system currently only supports a single depth. It takes the first path part after shapeshifter and looks for a contract named the same in the contracts directory at the root of the repo. That isn't going to work here unless we name the contracts using the team_design.
repo root ie. spearhead-canva-objects
contracts
teamId-designId.json
teamId-designId
fb911257-5f6c-4d19-942e-de9740435ecd.json
3c5a9a55-5eed-42db-81f3-1b9b1fa9334d.json
87b63da8-6065-4acc-b666-aefe8e3456c8.json
media
76c5813f-8712-4e12-ac4f-a4ea3988edeb.jpeg
05696c0c-189f-4ba4-b231-381cd163dd03.png
panelpage
teamId-designId.json
teamId-designId.json
teamId-designId.json
although panel page ids are currently generated a guid at random. Is it worth it to implement a solution to change the name?
Submit to /teamId-designId - given one form per design - right
The team-design must exist before submissions accepted.
What about media. Media currently only writes to media/*. We just need to rename with guid. Although we would really like to support paths like with entities.
How are contract schemas created from merely a panel page form. The structure can be immitated as converting entries to json. However, we also need to support things like validation and conditions (rules).
We can also go in a different direction and implement paths for contracts.
{
"id": "person.schema",
"path": "/ads/*/*",
"schema": {
"$id": "https://example.com/person.schema.json",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"age": {
"description": "Age in years which must be equal to or greater than zero.",
"minimum": 0,
"type": "integer"
},
"firstName": {
"description": "The person's first name.",
"type": "string"
},
"lastName": {
"description": "The person's last name.",
"type": "string"
}
},
"title": "Person",
"type": "object"
},
"userId": "b7a9bac5-5fef-4aa6-bf12-d536c156e453"
}
what about pages support in a design?
The text was updated successfully, but these errors were encountered:
rollthecloudinc/spearhead-canva-objects - private repo w/ pages site mapped to /public
The contract system currently only supports a single depth. It takes the first path part after shapeshifter and looks for a contract named the same in the contracts directory at the root of the repo. That isn't going to work here unless we name the contracts using the team_design.
repo root ie. spearhead-canva-objects
although panel page ids are currently generated a guid at random. Is it worth it to implement a solution to change the name?
Submit to /teamId-designId - given one form per design - right
The team-design must exist before submissions accepted.
What about media. Media currently only writes to media/*. We just need to rename with guid. Although we would really like to support paths like with entities.
How are contract schemas created from merely a panel page form. The structure can be immitated as converting entries to json. However, we also need to support things like validation and conditions (rules).
We can also go in a different direction and implement paths for contracts.
what about pages support in a design?
The text was updated successfully, but these errors were encountered: