eopo

Thanks for your work, but common practice is to keep separate features in separate branches, so that all changes regarding to this can be reviewed and handled separately. Looks nice...

Closes #512 Closes #504

I'm currently working on a feature that let's you create groups of aliases. Would it help you if you can choose groups your users can see?

Nope, ! would match the char `!`. Negating is nothing RegEx supports by default, but it could be added quite easily in JS

Nope. Highlighting/Replacing and Ignoring are two completely separate things, aren’t they?

How about accordion view. We could even enable them on desktop to view maps or other stored plugin data 🤔

Hmm, it might be better to include some sort of migrations system that adds the default value to configuration, when it isn't present on startup

I'll hack something together that runs on startup, checks for a config version variable in config.js and runs migration scripts found in a separate dir as needed.

Looks good, but I think we should make this a separate component and have every future change that needs something like config to be changed s separate file that gets...

Hello @denperss11 The answer is: Kind of. In fact, everything you mentioned is completely possible, but not very convenient. There isn't any kind of option for setting language, title, logo...