Open eoverfield opened 6 years ago
It's easier to go .Net standard vs Core for now, mostly due to Core being shitty supported in tooling for Azure Functions (per last week). Shouldn't really matter much, and could possible move later on when it's more mature.
Ok, signing up for a V2 already:) I like it. The best technology available today, that gets the job done in a reasonable manner seems best to me. I trust you judgement.
Still a bug with graph/AAD calls in SPFx, so cannot properly test this in my tenants.
is it wrong to say, "Im shocked..."
Azure function based api end point to work with modern theming.
Key points: This endpoint will begin to define the architectural blueprint for all other api endpoints. Issues to consider.
Verb: Get
Action: Get all custom themes or get one theme
Verb: Delete
Action: Delete a custom modern theme
Verb: Post
Action: Add a new modern theme, provide theme file
Verb: Patch
Action: update a provided theme