We’ve released a new minor version of the Forge CLI, @forge/cli@4.2.0 which includes the following update:
Fix for @forge/bridge history.location not updating when the route changes
This fix updates the location field within the history object. This occurs when the route changes and it’s returned from view.createHistory() .
To install the latest version of Forge bridge, run npm install @forge/bridge@latest in your resource directory.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
2 Likes
spall
#2
Hi @LashaniPerera,
that tweaked us in a few places.
Are there plans to make the history available in other/more modules (other than https://developer.atlassian.com/platform/forge/custom-ui-bridge/view/#createhistory) as well? We would be very interested in jiraServiceManagement:portalFooter:. We could then get the current portalId using the history. This would allow us to create a workaround for: I think I found a glitch in the jiraServiceManagement:portalFooter: module on the portal page
Best wishes and thanks for this update Andreas
2 Likes
system
closed
#3
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.