30 Jun 2021 - New external permissions, authorize method, CLI improvements, and bug fixes

:tada: ADDED - in Forge CLI version 1.5.0

This release includes:

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

:tada: ADDED - in Forge API version 2.1.0

We’ve added the authorize method, which allows app developers to authorize users and entities
(for example, issues, and pages) before making asApp product REST API calls. See the Authorize API documentation for more details.

Run npm install -g @forge/api@latest in your resource directory to install the latest version of Forge api.

:tada: ADDED - in UI kit version 0.13.1

With the new props appearance and openNewTab , you can now configure the Link component to appear as a button, and to open in a new tab. See the Link documentation for more details.

Run npm install -g @forge/ui@latest in your resource directory to install the latest version of Forge UI kit.

:no_entry_sign: REMOVED - in Forge CLI version 1.5.0

We’ve removed support for the login:ci command from the Forge CLI.

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

:wrench: BUG FIXES - in Forge api version 2.1.0

This release includes:

  • Compatibility with projects using Typescript versions earlier than 3.8.
  • The ability for developers to import and use the StorageAPI type in their code

Run npm install -g @forge/api@latest in your resource directory to install the latest version of Forge api.

:wrench: BUG FIXES - Compatibility with Node 14

Forge storage version 1.0.4 and Forge resolver version 1.3.2 are now compatible with Node 14.

In your resource directory, run the following commands:

  • npm install -g @forge/storage@latest to install the latest version of Forge storage
  • npm install -g @forge/resolver@latest to install the latest version of Forge resolver

:wrench: BUG FIXES - in Forge CLI version 1.5.0

This release includes:

  • Enable forge deployment and installation commands for apps with more than 20 installations.
  • A fix for fetch permission linter.

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

8 Likes

@XavierCaron the authorize api link leads to 404 Error page. Can you update the link, thanks :slight_smile:

Will there be an open-in-new tab feature in Custom UI as well?

4 Likes

@clouless - I think “open-in-new tab” is already possible via the Custom UI bridge router. navigate() method (as of 12 Apr 2021).

2 Likes

What a lovely release. Thank you.

@clouless Thanks for reporting this.

The official documentation was not live yet at the time of the post. It is resolved now, so all links should be fixed.

The associated changelog entry is also on our developer website

Sorry for the inconvenience.

1 Like

@XavierCaron Is there anything in regards to the Confluence Cloud Custom UI Search Users endpoint planned?
As per This Post, the ‘/wiki/rest/api/search/user’ endpoint docs state: This API resource doesn't support Oauth2 (3LO).
If this is not a bug, how are User Search requests meant to be made using Custom UI (Whilst UI-Kit UserPicker supports this, we are limited with UI-Kits functionality so require Custom UI) Requests to this endpoint using CURL, in Browser, or Postman work as expected, unless i’m failing to understand why this endpoint is different and it is just an issue with using Forge Custom UI?

1 Like

Hi @DennyMiller

Thanks for reaching out.
You can use the general Search endpoint instead: /wiki/rest/api/search?cql=<your_query_here>
(See: Search Documentation)
This endpoint supports 3LO and allows to use CQL for complex queries, such as user names.

For example:

const response = await asUser().requestConfluence(`/wiki/rest/api/search?cql=${`user.fullname ~ "${payload.search}"`}`)
const body = await response.json();

Where payload.search can contain things such as “John Doe”.

With this solution, you need the following permissions to your manifest:

  scopes:
    - 'search:confluence'

Hope this helps :slight_smile:

2 Likes

Thanks @XavierCaron, that works!
Question, how come the Search Users endpoint is different/not supported for Forge if the Search endpoint supports 3LO?
(It may also be good to state this in the Forge tab of the Confluence Cloud Search Documentation for future users)

Hi @DennyMiller ,
That Search User endpoint was overlooked, but as @XavierCaron mentioned, you can use the Search API and set the CQL’s type=user to search for users. We’ll be working on adding support for the other endpoint as well to be supported in Forge/OAuth.
Thanks,
Ryan

3 Likes