Open srobroek opened 3 months ago
A workaround i've implemented for this for now is by creating a separate ts file which exports the Types directly, which is working.
export * as net from '@aws-accelerator/config/lib/models/network-config.js'
export * as customisation from '@aws-accelerator/config/lib/models/customizations-config.js'
export * as replacements from '@aws-accelerator/config/lib/models/replacements-config.js'
and in the actual source:
import * as lzaCustom from '../schemas/customLzaConfig.js'
const test: lzaCustom.net.IDefaultVpcsConfig = {
delete: true,
excludeAccounts: ['bob']
}
Describe the bug The interfaces in config/lib/models/network-config.ts, customization-config.ts and replacements-config are not exported. This is not consistent with the standard exports defined in config/index.ts, where the classes are exported.
To Reproduce
import {INetworkConfig} from '@aws-accelerator/config/'
does not work.import {INetworkConfig} from '@aws-accelerator/config/lib/models/network-config.ts'
does work. Expected behaviorThe Interfaces related to the above classes should be exported through the index and be importable through the package.
Please complete the following information about the solution:
[x] Version: 1.8.1
[x] Region: N/A
[x] Was the solution modified from the version published on this repository? no
[x] If the answer to the previous question was yes, are the changes available on GitHub? no
[x] Have you checked your service quotas for the services this solution uses? N/A
[x] Were there any errors in the CloudWatch Logs? N/A
Additional context Add any other context about the problem here.