You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on the migration of this plugin in SAP Successfactors.
I noticed the new version has imported some new configuration such as type and paths. And I found there is a method called autoDetectType which will scan the ui5.yaml in the module root path to get the module type. It is wonderful and I really like this.
I suppose that this auto detect mechanism would find the paths I defined in the .yaml file as well. But so far it seems only reading the type property.
Yes, this is some missing part we currently have.
It's planned that we are using the UI5 Tooling APIs to get all relevant information about the project (incl. ui5.yaml). Right now we are manually parsing the file, which was just a quick solution.
karma v4.3.0 added support for plugins to be loaded async (karma-runner/karma#3297). This might be helpful as most UI5 Tooling APIs are async. This is the reason some parts within this plugin are done manually (e.g. reading ui5.yaml).
Hi Colleague,
I am working on the migration of this plugin in SAP Successfactors.
I noticed the new version has imported some new configuration such as
type
andpaths
. And I found there is a method calledautoDetectType
which will scan theui5.yaml
in the module root path to get the module type. It is wonderful and I really like this.I suppose that this auto detect mechanism would find the paths I defined in the .yaml file as well. But so far it seems only reading the type property.
Here is the
ui5.yaml
in my module,Just wonder if this plugin can detect the paths defined in this way so that I don't need add the paths into karma configuration again.
The text was updated successfully, but these errors were encountered: