Add type to Portal

[Noggling]

Expected outcome

A portal should have type field, this could be "ContextTypeDrivenPortal" or "AppDrivenPortal"

GET: api/portals/types

POST: api/portals

PUT: api/portals/{portalId}

if the portal type is "ContextTypeDrivenPortal" the body should include:

{
  // Portal data...
  type: "ContextTypeDrivenPortal",
  contextTypes: ["ProjectMaster"]
}

if the portal type is "ContextTypeDrivenPortal" and no contextTypes is provided the endpoint should produce a validation error.

if the portal type is "AppDrivenPortal" the body should include adn the contextType field can be empty:

{
  // Portal data...
  type: "AppDrivenPortal",
  contextTypes: []
}

Business Value / Developer Experience

Easier configuration and more understandable api

User Acceptance Tests (UAT)

All portal endpoints should receive and return type on the portal object.

Environments

All testing of issues are done in project-portal-test

• project-portal-prod
• project-portal-test
• project-portal-feature

For Backend use these

• project-portal-api-prod
• project-portal-api-test
• project-portal-api-feature

[kjetilhau]

I am not sure if I see the need for creating additional data, logic and thus more complexity on the backend/database for this. This can be inferred by checking whether there have been added contextTypes to a Portal or not.

So:

• ContextTypes == [] = Global
• ContextTypes == ["ProjectMaster", "..."] = Contextual / ContextDriven

If the only requirement for this issue is so that the frontend doesn't have to calculate this, we can supply something in the API view model