we stumbled upon something interesting today: We have a source file that defines some constants that contain a method that imports custom elements. They are route definitions for lazy loading.
Look at the following example:
Now if we import ERROR_ROUTE in some other file, lit-analyzer, will stumble upon ERROR_ROUTE and will then try to analyze routes.ts, but instantly exit due to the module depth. This seems to be generally desired, but in our case we would like to have routes.ts to be analyzed as well similar to how facade modules are analyzed today.
Hello,
we stumbled upon something interesting today: We have a source file that defines some constants that contain a method that imports custom elements. They are route definitions for lazy loading. Look at the following example:
Now if we import
ERROR_ROUTE
in some other file,lit-analyzer
, will stumble uponERROR_ROUTE
and will then try to analyzeroutes.ts
, but instantly exit due to the module depth. This seems to be generally desired, but in our case we would like to haveroutes.ts
to be analyzed as well similar to how facade modules are analyzed today.Thanks a lot, Christian