I don’t know. My eye doesn’t like doing that. I’d better leave it messy than do it by hand.
I never actually looking at imports. IDE solves it for me via quick info boxes which show fully qualified names and navigation which goes straight to implementation. Also it adds them automatically.
Overall there are two goals for the coding standard:
Make it human-readable.
Make merge fail less w/ nicer diffs.
As for #1, as I’ve mentioned, I saw imports grouped logically, not alphabetically and that makes more sense in some cases. Especially when domain layer is big and you’re working with more than a single bounded context. If we add the rule that everything should be sorted alphabetically we’re basically eliminating an ability to group imports in any other way.
As for #2, re-ordering or imports may affect diffs but it doesn’t really matter if these are ordered by name or not.