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
When defining the srcFiles with globs, like "srcFiles": ["./scripts/assets/tmp/**/*.svg"], I would expect the folder structure to remain intact. So input/24/foo.svg and input/32/foo.svg should be outputted to dist/24/foo.icon.ts and dist/32/foo.icon.ts. However, the current behaviour of svg-to-ts is to output as out/prefix-foo.icon.ts. Libraries like @svgr/cli do handle this correctly by default.
According to the reply in #196 , it is possible to define the config as an array but this is a needless hassle. An opt-in option to follow the current file structure would be much appreciated. And on that same matter, svg-to-ts currently does not output any warnings if it encounters a file with the same file name. So even though only one entity of foo.icon.ts is outputted while two have been given as input, the user is not warned of this. A warning would also be very welcome.
The text was updated successfully, but these errors were encountered:
When defining the
srcFiles
with globs, like"srcFiles": ["./scripts/assets/tmp/**/*.svg"],
I would expect the folder structure to remain intact. Soinput/24/foo.svg
andinput/32/foo.svg
should be outputted todist/24/foo.icon.ts
anddist/32/foo.icon.ts
. However, the current behaviour ofsvg-to-ts
is to output asout/prefix-foo.icon.ts
. Libraries like@svgr/cli
do handle this correctly by default.According to the reply in #196 , it is possible to define the config as an array but this is a needless hassle. An opt-in option to follow the current file structure would be much appreciated. And on that same matter,
svg-to-ts
currently does not output any warnings if it encounters a file with the same file name. So even though only one entity offoo.icon.ts
is outputted while two have been given as input, the user is not warned of this. A warning would also be very welcome.The text was updated successfully, but these errors were encountered: