Merlin Beutlberger

Glad to hear that. Please take care to open issues for `ui5-middleware-simpleproxy` in the community repository: https://github.com/ui5-community/ui5-ecosystem-showcase

Instead of enhancing the application type, @matz3 and I discussed the possibility of adding "component" types which are always served at their namespace (e.g. `/resources/my/todo/app`). Application projects would then only...

@sebbi08 The virtual path defined for a `module` project is always absolute. Also see [this documentation](https://sap.github.io/ui5-tooling/pages/Configuration/#resources-optional). To get the expected behavior, your shim would need to define the virtual path...

Hey @resitamas, this is one of many topics we are currently pursuing. So I can't give you an ETA. However we see great demand in such a type. Currently we...

@ecker fyi bullet no. 7

a63033f: Removed build phases as discussed today between @matz3, @tommyvinhlam, @codeworrior, @randombyte Build phases would allow for more precise extensibility of a types build execution. Mainly scenarios where only a...

In our internal discussions, one of the most controversial topics is whether the UI5 Tooling shall have characteristics of a *task runner* or that of a *collection of tasks*. Personally...

We discussed this again internally and would like to go forward with a simpler approach very similar to the proposal of @themasch. **[RFC 0004 Simple Build Extensibility](https://github.com/SAP/ui5-tooling/pull/54)** Please [have a...

Hey, we already have the general requirement to read (and write) files from a projects root directory. Therefore we are wondering whether you are only interested in the projects version...

Ok! We'll discuss this and may add the version information as an additional parameter to the custom task interface 👍 > passing in the whole package.json wouldn't hurt though IMO...