Hey @UlrichKuhnhardtIzym1 - thanks for sharing those.
- Web Triggers can be used to create your own REST endpoints attached to a Forge app as you can define your own arbitrary HTTP response to be returned from the Web Trigger. The only limitation (that I’m aware of) is that all requests to a Web Trigger must be POST requests, so you can’t do “semantically correct” REST (e.g. POST, GET, etc) - you can absolutely achieve the same functional outcome though.
- Profile Tab - Yeah good call, I’m assuming the use-case you’re thinking about is allowing users to create their own “user-specific” settings for apps? What context (other than the details of the user in question + their Workspace) would you want to have available there?
- TBH we need to do a full pass of the Project level in regards to Forge, not just settings page. Settings should take priority though since the Project is mostly a configuration container.
In terms of what checks we need to pass before the next phase, my view is that we need to have a clearly documented, “production-ready” way to solve all the existing Connect use-cases before we consider any kind of “next steps”.
Now I do want to be clear, solving all the Connect use-cases does not necessarily mean providing all the exact-same features. API Proxy is an excellent example - I’m hoping there is a way we can solve that “use-case” in a way that is a bit more… conventional. I know it’s basically a meme that “every product includes a non-standardised, undocumented, totally proprietary equivalent of GraphQL” - but API Proxy takes that to a new level.
Would be great to get your feedback re: Web Triggers and whether you see them as a viable equivalent.
@JanNylund - thanks for sharing that! I can’t give you a specific timeline, but we will include this in the list of items that need to be delivered before we enter any next-phase of the process.
Could you share some info in terms of what context you’d like provided from the host app to be passed to that module? I’m assuming:
- Repo, Project, Workspace context
- Information about the file-path/name
- Maybe latest commit hash??
- Anything else?
FYI - I will be off on medical leave for the next 2 weeks, but will loop back to this thread when I return. @HamreetKaur will be making sure the mentioned RFC is published before then.