I propose adding a section to the Plugin-How-To section of the wiki that offers guidelines about how to implement each EditorConfig property.
Some rules are best implemented the moment you open a file, but others may only apply on each file save. We probably need some clarity there.
To kick-off the discussion, let me make a list and we can modify it as the discussion evolves.
Sure, I'm totally up for it.
Just a question.
What if for instance the eol in the file is crlf and the file is opened and .editorconfig sees it should be lf. Should the plugin convert silently, convert and report, just report, offer an option to do the conversion. We should say something about that as well.
It would be pretty annoying if you get a prompt every time someone opens up a file with mixed line endings. I think the description above is sufficient. The only thing you should do on file open is activate the editor setting. In some editors (e.g., vscode), this will mark the file as dirty. In other editors, it won't, so you wait until they save the file to perform any eol conversion. @ffes, does that make sense?
Maybe we should say "activate" instead of "apply" editor setting? Would that be more clear?
I've added a Plugin Guidelines wiki page with a reference to it on the Home wiki page. Feel free to continue any discussion points here, but I'm closing the issue for now.