Web trigger API updates, CLI improvements, and bug fixes

:tada: ADDED Web trigger API

A webTrigger.getUrl method has been added to the @forge/api package to programatically obtain web trigger URLs from within your app. See the web trigger API for more details.

:sparkles: UPDATED Web triggers

Web triggers will now parse query parameters. See web triggers for more details.

:sparkles: UPDATED Linting for egress controls

forge lint now detects missing egress manifest fields for fetch calls and can add these fields when running forge lint --fix.

:sparkles: UPDATED installContext in Forge resolver version 1.2.0

Backend functions are now passed installContext in context. See custom UI resolvers for more info on resolvers.

Run npm install @forge/resolver@latest in your app directory on the command line to install the latest version of Forge resolver.

:wrench: BUG FIXES - in Forge API version 1.2.0

  • The fetch, requestJira, and requestConfluence API methods now supports setting the content-type header to other values, such as 'application/x-www-form-urlencoded'. The default content-type remains 'application/json'.
  • A fix for properties.onConfluenceSpace with personal spaces.

:wrench: BUG FIXES - in Forge CLI version 1.3.3

  • A fix for custom UI tunneling when using Linux.
  • A fix for removing user grants when uninstalling.

Run npm install -g @forge/cli@latest on the command line to install the latest CLI version.

We have more exciting changes in the works, so stay tuned!

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.