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
Currently web components projects use own TypeScriptFileUpdate.ts file, located inside their own folder. It duplicates much of the logic inside the "general" file placed under "packages/core/typescript".
All projects must use the general file. It should be updated to support generation of project different than Angular.
N. B. The logic should be platform agnostic. Where we check for Ng stuff - we should set it as parameters instead of looking what platform the generated project is.
We should refactor the addRoute method. This method is actually doing two things, at least. It adds routes as well as it adds imports. We should try to split this into two separate methods. Note, to do this we may need to create separate visitor for imports and routes. - #1060 (comment)
Ignite UI CLI version: 9.x.x
Framework: Web Components
Project type: igc-ts
The text was updated successfully, but these errors were encountered:
Description
Currently web components projects use own TypeScriptFileUpdate.ts file, located inside their own folder. It duplicates much of the logic inside the "general" file placed under "packages/core/typescript".
All projects must use the general file. It should be updated to support generation of project different than Angular.
N. B. The logic should be platform agnostic. Where we check for Ng stuff - we should set it as parameters instead of looking what platform the generated project is.
We should refactor the
addRoute
method. This method is actually doing two things, at least. It adds routes as well as it adds imports. We should try to split this into two separate methods. Note, to do this we may need to create separate visitor for imports and routes. - #1060 (comment)The text was updated successfully, but these errors were encountered: