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, the src base is set to the public directory, but I think it would be useful to add an option that allows users to customize the base directory.
Why?
Some users might prefer to store SVG assets within the src folder instead of the public directory.
Even when using the public directory, assets are often organized within an assets folder, so having to specify paths like assets/svgname.svg repeatedly can be inconvenient.
Proposal
Introduce a base option to set a custom directory from which SVGs are resolved. This way, users can easily define where their SVG files are located.
Allow users to reference SVGs without explicitly including the .svg extension. For example, typing svgname would automatically resolve as svgname.svg.
Benefits
Improved flexibility for asset organization.
Enhanced developer experience with shorter and more intuitive path references.
If this proposal sounds good, I'd like to take a stab at implementing it. What do you think?
The text was updated successfully, but these errors were encountered:
Description
Currently, the
src
base is set to thepublic
directory, but I think it would be useful to add an option that allows users to customize the base directory.Why?
src
folder instead of thepublic
directory.public
directory, assets are often organized within anassets
folder, so having to specify paths likeassets/svgname.svg
repeatedly can be inconvenient.Proposal
base
option to set a custom directory from which SVGs are resolved. This way, users can easily define where their SVG files are located..svg
extension. For example, typingsvgname
would automatically resolve assvgname.svg
.Benefits
If this proposal sounds good, I'd like to take a stab at implementing it. What do you think?
The text was updated successfully, but these errors were encountered: