[Fix] group-exports: Flow type export awareness

[ernestostifano]

Fix for [#1702].

Now export and export type statements are handled separately with the same logic.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling baf1a8c on ernestostifano:feature/issue-1702 into 6a110dd on benmosher:master.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling 4207cba on ernestostifano:feature/issue-1702 into 71ca88f on benmosher:master.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling 4207cba on ernestostifano:feature/issue-1702 into 71ca88f on benmosher:master.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling 4207cba on ernestostifano:feature/issue-1702 into 71ca88f on benmosher:master.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling 4207cba on ernestostifano:feature/issue-1702 into 71ca88f on benmosher:master.

[coveralls]

Coverage increased (+0.007%) to 97.804% when pulling 4207cba on ernestostifano:feature/issue-1702 into 71ca88f on benmosher:master.

[ernestostifano]

Note: If .idea files shall be kept, then .idea/codeStyles/Project.xml and .idea/inspectionProfiles/Project_Default.xml can be adjusted to match project rules. If not, then .gitignore changes can be reverted and the whole .idea directory can be deleted.

[ernestostifano]

I will close this pull request and make a new one with a simpler commit history. Current commits have wrong author data (Sourcetree messed up).

[ljharb]

Please do not do that - please restore the branch and reopen this PR.

[ljharb]

I can help you rebase this one, but a new PR makes clutter i can never ever clean up.

[ernestostifano]

I tried several ways to amend commits author data with no success. Should I restore the deleted forked repository? Can I fork it again and point this pull request to a new branch? I have saved all the changes I made, so no work is lost. Please let me know.

[ljharb]

Ah, if you deleted the fork, then that’s unrecoverable. In the future, please don’t delete a fork with an unmerged PR.

Maintainers can always clean up the branch before merging.

[ernestostifano]

I am sorry if I did wrong. Lesson learned. Should I create a new PR with the issue fix?

[ernestostifano]

@ljharb wrote to GitHub. Everything is restored. When you have time, we can clean up commits.

[ernestostifano]

Why have coverage decreased if it was increased before? Also why are not all checks passing now?

[golopot]

Some tests are skipped in older eslint versions. CI jobs with older eslint report lower coverage. Therefore sometimes coveralls reports decreased coverage randomly.

[ljharb]

@ernestostifano thank you! I've rebased it, and removed the .idea stuff which belongs in your personal global gitignore, and not in every project you happen to touch. I'll review soon.