-
Type:
Suggestion
-
Resolution: Obsolete
-
Component/s: Ecosystem
Currently, we send a non-existent hash d41d8cd98f00b204e9800998ecf8427e (the hash of the empty string) to the add-on when a new macro is created. Trying to resolve this hash results in a 404.
If there is no body yet, we should not send a hash to the add-on.
If you are previewing a macro, the body should be available to the addon.
Moved to unbundling app fire epic
- blocks
-
CONFCLOUD-60993 Provide content.id to custom macro editor
- Closed
-
CONFCLOUD-61267 Add draft_id to the available Confluence properties
- Closed
- is blocked by
-
CONFCLOUD-60638 Update documentation for getMacroBody
- Closed
- is duplicated by
-
CONFCLOUD-60957 Provide Macro preview for Remote Macros that have a body
- Closed
-
CONFCLOUD-61261 Custom Editor url should be able to identify new or editing page
- Closed
- is related to
-
CONFCLOUD-60803 Clarify options for previewing macro body content
- Closed
- relates to
-
CONFCLOUD-60715 Dynamic macros should be able to previewed
- Closed
-
CONFCLOUD-61044 Create iframe according to the rendering method specified in context
- Closed
-
CONFCLOUD-61057 Allow atlassian-connect-express validate JWT's hash in payload
- Closed
-
CONFCLOUD-61135 Allow dynamic and static macros be rendered with POST
- Closed