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
Generate a workspace and an application using the @o3r/create generator
Add an application with npm run ng g @o3r/workspace:application test.
Run npm run ng add @o3r/rules-engine -- --project-name=test.
Generate a component using the npm run ng g component my-component command.
Convert the component into a rules-engine compatible component with the command npm run ng g rules-engine-to-component -- --path=apps/test/src/components/my-component.component.ts
Current result
The module RulesEngineRunnerModule is neither imported at app nor component level.
Expected result
The ng add script should add an import of the RulesEngineRunnerService module in the config.ts (or app.module.ts) in the application. This should not be a manual step.
In a similar fashion, the same module should be imported in the component's import list (in the module or the decorator of the module depending on whether the component is standalone or not) when running the npm run ng g rules-engine-to-component command.
Additional comments
No response
The text was updated successfully, but these errors were encountered:
Package name
rules-engine
Package version
10.0.3
Reproduction steps
npm run ng g @o3r/workspace:application test
.npm run ng add @o3r/rules-engine -- --project-name=test
.npm run ng g component my-component
command.npm run ng g rules-engine-to-component -- --path=apps/test/src/components/my-component.component.ts
Current result
The module
![image](https://private-user-images.githubusercontent.com/110408057/330868329-2cd7c096-a81e-4768-bb66-21dab3ef5f6a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NTExMjQsIm5iZiI6MTcyNDQ1MDgyNCwicGF0aCI6Ii8xMTA0MDgwNTcvMzMwODY4MzI5LTJjZDdjMDk2LWE4MWUtNDc2OC1iYjY2LTIxZGFiM2VmNWY2YS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyM1QyMjA3MDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02OTlkNjlmZmU1ZTEzZDc3NmY5ZjA3NTJiMDhkZDFkYTBjYWFmNjc2Mzg5OThlMTRiOTY2MzY0MDlhZGM5Y2M5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.lOOhL4nz2l1bPg8P91jA_si9h4rJ1J7pJF9lGuYsdYg)
![image](https://private-user-images.githubusercontent.com/110408057/330868536-4c7d6c27-7e73-41ee-81a7-5c3eaf268bd1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NTExMjQsIm5iZiI6MTcyNDQ1MDgyNCwicGF0aCI6Ii8xMTA0MDgwNTcvMzMwODY4NTM2LTRjN2Q2YzI3LTdlNzMtNDFlZS04MWE3LTVjM2VhZjI2OGJkMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyM1QyMjA3MDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zYjJhZjIyMjYyMjc2NjU5MTY4OTJiMjJiMmY4ZTJhYzUwMGY0ZTdhYjhkNzUyMDc4NmRmMWE1NDI0MGU3MThiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.b6Mc3QVkE8h4ddYbyY5oi3OZU4Qtc2vPnnSC3kykT7w)
RulesEngineRunnerModule
is neither imported at app nor component level.Expected result
The ng add script should add an import of the RulesEngineRunnerService module in the config.ts (or app.module.ts) in the application. This should not be a manual step.
In a similar fashion, the same module should be imported in the component's import list (in the module or the decorator of the module depending on whether the component is standalone or not) when running the
npm run ng g rules-engine-to-component
command.Additional comments
No response
The text was updated successfully, but these errors were encountered: