[x ] Bug report
[x] Documentation issue or request
@GregOnNet
Current behavior
When you add metaui to existing project using ng-add there is a Dummy.oss file created. which is confusing.
This file is need to be able to compile project as ApplicationModules imports user-rules.ts. Without Dummy.oss this file is empty.
Remove Js comments from generated Domain classes
Expected behavior
Let's improve it a bit. Each application needs also 1 common rule file with application scope called Application.oss. Will rename dummy.oss to this file instead. When rules are added it will have default app rule file to start with, where you can start defining global rules ('custom layouts', landing page structure, global actions, etc.. )
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
I'm submitting a...
@GregOnNet
Current behavior
When you add metaui to existing project using
ng-add
there is a Dummy.oss file created. which is confusing. This file is need to be able to compile project as ApplicationModules importsuser-rules.ts
. Without Dummy.oss this file is empty.Remove Js comments from generated Domain classes
Expected behavior
Let's improve it a bit. Each application needs also 1 common rule file with application scope called
Application.oss
. Will rename dummy.oss to this file instead. When rules are added it will have default app rule file to start with, where you can start defining global rules ('custom layouts', landing page structure, global actions, etc.. )Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?