Feature Request - Add Fix feature to warnings

[garretthyder]

Hi @Mte90

Had a thought for Warnings I wanted to run by you. Was thinking it would be nice to have a 'Fix' link on the warning which would correct the issue for you.

For instance the ... translate to … warning;

Rather than having to copy the … in or type it you could just click a link and it's correct the issue and discard leaving the Add translation to you.

Thought GlotDict would be a better place to approach that before raising in GlotPress.

Let me know what you think and i'll start playing around with it.

Cheers

[Mte90]

I think that is not bad and require a lot of work so is perfect for the next release :-D

[garretthyder]

Sounds good, I'll put some time into this next chance I have. Feel free to assign my way

[garretthyder]

To start the GlotDict warnings on translations are as follows;

• Validation for final "...", ".", ":"
• Validation for final ;.!:、。؟？！
• First character is not uppercase on translation
• Missing term translated using the locale glossary
• Check for curly apostrophe Reference - https://github.com/Mte90/GlotDict/blob/master/README.md

As to GlotPress it looks like they've got the following;

• warning_length
• warning_tags
• warning_placeholders
• warning_should_begin_on_newline
• warning_should_not_begin_on_newline
• warning_should_end_on_newline
• warning_should_not_end_on_newline Reference - https://github.com/GlotPress/GlotPress-WP/blob/5e53ec512bc2b77e112ae13474c677f85e67599b/gp-includes/warnings.php#L121

[Mte90]

We implemented a way to close warnings but no autofix. Maybe is better to move on 1.5?

[garretthyder]

That's awesome @Mte90 that dismiss will be a huge bonus for this release and I've punted this to 1.5 as it's going to be quite an involved implementation that deserves it's own release