Thanks for letting us know about this, I have corrected the link just now. It was supposed to link to this article:
In that article, you will find quick info on how to use UI components and also a few useful links to the Backoffice Storybook: @storybook/core - Storybook
And the Backoffice JavaScript documentation, where you can find info about contexts and types: @umbraco-cms/backoffice
Bit of a long shot but here goes:
Do you happen to know if there’s any place where the classes for the backoffice javascript docs are more thoroughly described?
For example, I am trying to build an extension that gets a document and its property values.
I can call it and get the document but I don’t get any property values. So I am doing something wrong.
Here I am hoping to be able to read somewhere, something like “Use this to get the full document including property values” or something similar.
The docs here however in general only says:
This mixin enables a web-component to host controllers. This enables controllers to be added to the life cycle of this element.
for many files which is confusing.
Unfortunately, it is not well documented. You would have to figure it out through the source code, but this might get you going:
Consume the UMB_PROPERTY_DATASET_CONTEXT, a context class that holds the values of the current entity, so it would work inside property editors, workspace views, and so on:
You can find properties on it and set values on specific properties – here I have two variables, the first one holds all properties and the second one holds a value of a specific property by alias.
Thank you! This helps immensly. Grasping the terminology and its use cases seems to be the hardest part of extension building for me right now.
Do you happen to know if one should use a context to fetch other documents than the one you are currently editing? Trying to answer myself the question “am I using context, repository, or both?”
No, in that case you would need to fetch the document through a repository. The context only holds information about the entity currently being shown on the screen. You could use the UmbDocumentDetailRepository in that case.