Context Navigation

Changes between Initial Version and Version 1 of Ticket #34050, comment 1

-              initial
+              v1
 Can confirm this.
 It's worth highlighting is that migrations literally copies the constraint name verbatim for **any** invalid Python module character not just dots "." and will happily apply these (as long as there's no dots) – as long as we're not doing any imports of migrations we should be fine.
+It's worth highlighting is that migrations literally copies the constraint name verbatim for **any** invalid Python module character not just dots "." and will happily apply these (as long as there's no dots) – if we're not doing any imports of migrations we should be fine.
 The PR replaces the dots with underscores - that's one solution which addresses the immediate issue but I'm just wondering whether:
 a.) Any invalid character is replaced to ensure there are no more problems like this; or
 b.) Migrations (ie `showmigrations` and `migrate`) do not look skip files with multiple dots?
+b.) Migrations (ie `showmigrations` and `migrate`) do not skip files with multiple dots?