Query parameter name for SVG

[webdiscus]

Created from the comment of the #154 issue.

Thoughts on SVG import in HTML:

The SVG import will take into account the settings of Webpack modules. In other words, the default import behavior fully corresponds to the Webpack options unless the query parameters indicate different behavior.
What I do not know:

Whether the above behavior can be implemented.
How much time it might take.
How the implementation of such behavior might affect performance.
The query parameter name (considering semantics and usability):

replace
Semantics: Clear and direct, it communicates that the img tag will be replaced.
Usability: Simple and intuitive, easy to understand at a glance. Works well for the main action.

substitute
Semantics: Similar to "replace," but has a slightly less common usage in technical contexts. It may imply an alternate replacement rather than the default behavior.
Usability: Less immediate clarity compared to "replace."

transform
Semantics: Suggests a change in the structure or format. Could work if the focus is on converting an img to an svg.
Usability: Useful but may feel more general than specific to replacing the parent and inheriting attributes.

swap
Semantics: Suggests an exchange, which might confuse users since there’s no bidirectional replacement (just img to svg).
Usability: May cause misunderstandings, as “swap” implies a two-way process.

merge
Semantics: Implies a unification or combination of two elements, which fits the idea of inheriting attributes. However, it doesn’t inherently communicate the replacement action.
Usability: Could be misleading unless the merging of attributes is the primary focus.

embed
Semantics: Highlights inserting the SVG, but doesn’t clearly indicate the replacement or inheritance aspect.

integrate
Focuses on the idea of embedding the SVG while preserving or inheriting attributes.

inherit
Highlights the aspect of adopting attributes, making it clear for users that inheritance is a key feature.

adopt
Similar to "Inherit," but slightly less formal, giving a sense of attribute adoption during the process.

convert
If the emphasis is on the transformation of the tag to an element.

assimilate
A more unique and descriptive term for merging the parent attributes into the SVG while replacing the parent element.

---

@vralle This is good base for using in new features.

[vralle]

This text was written in the upcoming changes content in version 4.19.

As for the name of the query parameter, the changes already implemented embed. The parameter name is perhaps not ideal. The semantics are close to importing files with raw parameter and do not fully reflect the actions of the handler. There may be a misunderstanding of the plugin's actions when using this query parameter, but a warning is implemented in case of improper use.
I do not foresee any conflicts at the moment.

But if we rely on semantics, integrate or assimilate might be suitable candidates for the query name. Additionally, such names will be easier to search through the codebase if needed, since I assume these words are used less frequently.

To sum it up, I don't see any compelling reason to change the parameter name at this point, except to improve semantics.

[vralle]

The SVG import will take into account the settings of Webpack modules. In other words, the default import behavior fully corresponds to the Webpack options unless the query parameters indicate different behavior.

I have nothing to add, as I can only rely on my experience using the plugin. The change in the behavior of the SVG import in version 4.19 matches my expectations. I haven't looked under the hood at the moment. My involvement in the development of the plugin is close to zero. If this changes, I can add details.