-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Minor
Issue Summary:
The usage of the useProductContext() triggered by the module (confluence:contentAction) is missing the content.type value in the returned object:
Steps to Reproduce
- Create a confluence:contentAction app
- Add the useProductContext and use it
- Inspect the returned object, notice that it doesn't contain the type
Expected Results
Since the documentation informs about the subtype, and similar modules also include this information, it's expected that this module also contains the type property.
Actual Results
The returned object doesn't contain the content.type property
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available