Support string replace option on the autofilling

I have created an option for string replacement, attaching screenshots and a video for reference.

Please review.
Thank you

I love it that you already did this!

Exactly what I needed, except that I would have let the developer/site builder specify the patterns.
I do think this is a good addition but maybe the naming is not correct in this case.
Maybe we can change the title to say for example "Transform to anchor" instead of string replacement?
Then we should also update the issue title and summary here to reflect the change.

With that said now onto the functionality, did you test every specific case? Like special characters and symbols? We should strip out every character that is allowed to be entered in the textfield but not allowed in the anchor definition.

Setting this to needs work for 2 things:
1. Update issue title/summary if we keep this implementation. Update the label and machine name of the field.
2. Test more scenario's and make sure we only keep valid anchor text.

Also check the pipeline issues please. Keep an eye on Coding Standards, CSpell, ESlint , ...

@tim-diels Thanks. Please provide a detailed description of what we want. Should we create a field in the widget where the pattern is defined by the developer? Then, we can create the functionality according to that.

I want to thank you for the already work done as it inspired me to think further on how to handle this.

I would suggest we think about this broader and allow other options to the autofill. So I would call it modifiers.
So first we need to have an option to enable the modifiers as this is only needed for specific use cases and not the default option.
After that we should be able to have modifiers, in this use case its only one for now called "Anchor". So this will allow other feature requests or persons to add modifiers as they want.

I adjusted the summary and title to reflect the required changes. I hope that's ok for you?
Thanks you for being so flexible already and the effort you put into this.

@tim-diels Thank you for your description of modifiers. I have now created the option to enable modifiers. In the custom replacement character, we should define the character by which we can replace a space. I have also tested that autofill with string modifiers works fine with special characters and symbols it can remove special characters and symbols automatically during autofill.

I have attached the video for reference.

Also, the Gitlab pipeline now passing with no errors or warnings.

Please review.

Thank you

Thanks for the adjustments, I really like you're activity on here. I just have a small remark where there is a difference in config schema keys and form keys.

It gives now an error 'modifier_type' is not a supported key.

Hi, i made the little change in the schema file.
Best regards.

Thanks, this looks good for me.

Still have one issue that the slugify is not complete. You can now have consecutive hyphens.
I saw https://dev.to/bybydev/how-to-slugify-a-string-in-javascript-4o9n where there's a nice example of a complete slugify function.
Maybe we should look into using this

function slugify(str) {
  str = str.replace(/^\s+|\s+$/g, ''); // trim leading/trailing white space
  str = str.toLowerCase(); // convert string to lowercase
  str = str.replace(/[^a-z0-9 -]/g, '') // remove any non-alphanumeric characters
           .replace(/\s+/g, '-') // replace spaces with hyphens
           .replace(/-+/g, '-'); // remove consecutive hyphens
  return str;
}

Or at least the "remove consecutive hyphens"