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
The generated app has the data but the reference path is not the proper one, because in the sample itself the hierarchy is deeper and the path is import { INVOICE_DATA } from "../../../data/invoiceData"; .
The text was updated successfully, but these errors were encountered:
This problem has 2 workarounds:
1 - change invoicedata.ts file location so that the final file structure fits the import statements
2 - remove the shortenComponentPathBy
The fix for this will include a lot of changes... We will have to first check if there is a shortenComponentPathBy for the respective config, if yes, then check the config's component content for relative paths and if yes then glue up all the path pieces for every additional import and the path pieces for the respective component for a config and if the relative path for the component does not fit the path for a single additional import. then change the relative path inside the component based on the value of shortenComponentPathBy. @zdrawku I am not sure that this will be an efficient approach (it does not sound like one) for the solution of this issue, but for now it is all that we got, so should we continue with this issue or just postpone it and hope something better comes in as a plan?
The ExcelExportSample1Component has the following configuration:
The generated app has the data but the reference path is not the proper one, because in the sample itself the hierarchy is deeper and the path is
import { INVOICE_DATA } from "../../../data/invoiceData";
.The text was updated successfully, but these errors were encountered: