Migrations drop and recreate foreign keys - even on "empty" migrations?

[bragma]

I'm puzzled by the migrations generated by ef7. It seems that they first drop all FKs, then they create them back. I'm not sure why this is needed. What's even more puzzling is that the migrations generator can't understand a "useless" or "empty" migration, and still generate one even if nothing has changed in the code or DB. Just adding a migration creates code that drop and recreates FKs.
Is understanding if a migration is required totally in developer's hands? I hoped for the generator to understand if anything changed and else report "no migrations needed" or something similar...
If it's not the case, I foresee a lot of troubles ahead. I.e. developer creating migrations just because they don't recall if anything has been changed or forgetting to create migrations.

[flagbug]

I'm seeing this too, especially with Asp.Net Identity

See aspnet/Identity#697

[smitpatel]

dupe of #3751 . It has been fixed already and will ship in RC2.

[bragma]

Thanks for pointing out the fix. I failed to see the issue closed while searching for clues.