Functions - dev UX improvement pack

[arturskorupa]

Description

UX of developer working with functions can be better. Let's consider the following improvement pack:

• Display function's pod output directly at the function view (currently user has to go to pod)
• Provide a kind of dev tools for functions. A popup (or side panel) can be displayed. It should let user to see the output of function, let user send something on function input (internally, without API rule)
• Code snippets should be available (for most commonly used patterns like execute a API call to the service, simplified extraction of BTP service's access data, something similar for eventing, execution of function in a chain, etc.)
• Provide a plugin for VS code to move the development to more sophisticated tool.
• Function edit popup can be closed when Esc key is pressed, without any notification of the user. All data entered can be lost.
• Add possibility to expand function source section. It's currently adjusted to the screen size, but further adjustments by user aren't possible.
• Add possibility of saving function without building. Because I can easily lose all the data (esc key pressed) I save function more often, and it triggers rebuild (which consumes resources) . At least it should be possible to update the function (with rebuild) but without closing the edit popup.
• incomplete autocompletion is more misleading than helpful. I wanted to use process.env, while the autocompletion list doesn't present such option.

Consider creating another page for function development (in addition to the existing one, more generic, for function resource). On Function development include features listed above, and remove sections for replicas and , events - those place can be reused for snippets and debuging.

Reasons

Better UX can improve adoption of serverless. Currently too much time is wasted for non-development activities (like looking for function output), especially among less experienced users of serverless.

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale