[APIv2] Project Resource Type Controller
Project Resource Type Controller
For this controller we will likely face some non-backward compatible changes. When relying on these features you can subscribe to notifications on this issue and/or engage into the discussion. Changes will be announced here.
Discussion points are classified as follows:
-
⚠ ️ May introduce breaking change. -
💡 Addition to existing interface -
❓ Open question, further discussion will be done in this thread
Discussion
ResourceTypeInformationDto
-
❓ Why is this notResourceTypeDto
? Probably because it was already taken byresources
Endpoint. See discussion above onoptions
. Likely, the Dto then can be reused. -
💡 Add propertydisplayName
-
⚠ ️ "merge"can*
andis*
properties to intermediate object"features": {"canCreate": true, ...}
-
⚠ ️ addresourceContent
asview
tofeatures
from above. Alternatively, merge content intofeatures
(e.g.resourceContent.metadataView.editableKey
becomesfeatures.metadata.hasEditableKey
). -
❓ I have the feeling that somecan*
properties are redundant toresourceContent.*
properties; e.g.,canUpdate
&canDelete
toresourceContent.readOnly
. Maybe this needs some cleanup. -
⚠ ️/❓ Depending on the discussion above, consider merging some of thefeatures
by "area" likestorage
(for file storage related e.g.canRead
),resource
(for general resource related e.g.,isQuotaAvailable
) -
⚠ ️/❓ Is there an alternative forgeneralType
andspecificType
? maybeservice
andregion
(orinstance
)? -
❓ /💡 Is theresourceCreation
property used? I did not find it. If not➡ ️ remove.
Edited by Marius Politze