tcmts.cli.test.e2e.cycles

testClassEditedAlone () => void

One member of a cycle with a class is edited alone, though alone it wouldn't check: the class has private state.

testCycleMateImportsDontClash () => void

Editing one member of a cycle whose other member imports a name the file uses for something else: the other is written importing it by another name (`Move_1`), rather than the save being refused

testCycleUpdatedWhole () => void

A cycle is updated whole: changing one member saves the rest with it, so none uses an old one.

testCyclesAreWarnedAbout () => void

Saving says when it makes a cycle worth avoiding: one only types make (an interface breaks it), or a big one of code calling itself; two functions recursing together, and a cycle saved again as it was, aren't mentioned

testNoCircularImports () => void

No circular imports: definitions that refer to each other are stored together, as one module, so the modules code runs from import each other without ever going round in a loop (no import order to get wrong, nothing half-loaded)

testUpdateMakingACycle () => void

An update that makes a cycle (the new code uses one that uses it) saves the other with it: they're hashed as one.