oasisdigital / atlassian-tooling Goto Github PK

Currently we only generate the atlassian.connect.json once on the start of the serve executor. It would be great if we could improve this experience and regenerate this file if any of the template/.env file inputs change. This way the user doesn't have to restart the serve executor.

Current list of commands that need to be added:

• install list sub-command (link)
• contributors(link)
• environments(link)
• logs(link)
• providers(link)
• register(link)
• settings(link)
• storage(link)
• variables(link)

Currently the user has to manually install the app via the ngrok install url to their preferred Atlassian site. It would be awesome if we could automatically due this with a domain/token they provide.

Currently we hard code the express port for the ngrok tunnel. This should pull from the port of the express server that is spun up as a part of the serve executor.

You cannot use Connect's JS API within a forge application. This will be a huge point of migration for people to really get something out of this plugin/migration system.

To replace the Connect JS API, Forge has a UI Bridge & Resolver system that allows the frontend application to communicate with the host server system and provide similar API capabilities to the Connect JS API via the @forge/api package.

Docs for the Bridge system
Docs for the Resolver system

Tasks Left To Perform:

• Asses current parity of Resolver/Bridge system with Connect's JS API. Create tasks below for each piece that we can reasonably migrate.

Currently we only support the @nx/angular app executor type for the forge application generator. It should be fairly easy to support the @nx/react app executor type. We really only need to pull out the dist location that that app is built to.

https://nx.dev/nx-api/react

Currently those code is a bit of a mess with nested runExecutors and for await loops. If this can be rewritten to make more sense and be more maintainable that would be for the best. Potentially rewritten using RxJS?

Currently the user has to install ngrok globally and authenticate themselves (setup part of our instructions). It would be better if we just incorporated this into our serve executor to check if the user has ngrok authenticated and if they don't we run it ourselves for them to provide the info to the prompts. Avoiding the global install.