James Bardin 22dc685052 check for nested module index changes ... Changing only the index on a nested module will cause all nested moves to create cycles, since their full addresses will match both the From and To addresses. When building the dependency graph, check if the parent is only changing the index of the containing module, and prevent the backwards edge for the move.		2022-01-04 09:20:47 -05:00
..
testdata	find implied moves in nested modules	2022-01-04 09:20:47 -05:00
move_execute_test.go	refactoring: Move nested modules	2021-12-21 16:25:06 -05:00
move_execute.go	check for nested module index changes	2022-01-04 09:20:47 -05:00
move_statement_test.go	find implied moves in nested modules	2022-01-04 09:20:47 -05:00
move_statement.go	find implied moves in nested modules	2022-01-04 09:20:47 -05:00
move_validate_test.go	check for nested module index changes	2022-01-04 09:20:47 -05:00
move_validate.go	add AffectedAbsResource to interface	2021-11-16 18:19:11 +00:00