Codeflower

Juro Oravec

2020-04-08

Very useful for gaining insight into project structure, reviewing whether the structure is suitable and finding suggestions for refactoring and restructuring.

Example: Rendered one of the projects I worked on with CodeFlower, discovered that in frontend components there was one file which was X times larger than the rest, and realised that the file actually harboured multiple functionalities and should be most likely split into individual components.

Note, however, that since CodeFlower uses D3, there's a limit to what it can render. Small- and mid-sized projects are fine. But, rendering died when I tried to use it on TypeScript repo (which has 1.20 GB at the time of writing this).

Juro Oravec

2020-04-08

Very useful for gaining insight into project structure, reviewing whether the structure is suitable and finding suggestions for refactoring and restructuring.

Example: Rendered one of the projects I worked on with CodeFlower, discovered that in frontend components there was one file which was X times larger than the rest, and realised that the file actually harboured multiple functionalities and should be most likely split into individual components.

Note, however, that since CodeFlower uses D3, there's a limit to what it can render. Small- and mid-sized projects are fine. But, rendering died when I tried to use it on TypeScript repo (which has 1.20 GB at the time of writing this).

Juro Oravec

2020-04-08

Very useful for gaining insight into project structure, reviewing whether the structure is suitable and finding suggestions for refactoring and restructuring.

Example: Rendered one of the projects I worked on with CodeFlower, discovered that in frontend components there was one file which was X times larger than the rest, and realised that the file actually harboured multiple functionalities and should be most likely split into individual components.

Note, however, that since CodeFlower uses D3, there's a limit to what it can render. Small- and mid-sized projects are fine. But, rendering died when I tried to use it on TypeScript repo (which has 1.20 GB at the time of writing this).

Juro Oravec

2020-04-08

Very useful for gaining insight into project structure, reviewing whether the structure is suitable and finding suggestions for refactoring and restructuring.

Example: Rendered one of the projects I worked on with CodeFlower, discovered that in frontend components there was one file which was X times larger than the rest, and realised that the file actually harboured multiple functionalities and should be most likely split into individual components.

Note, however, that since CodeFlower uses D3, there's a limit to what it can render. Small- and mid-sized projects are fine. But, rendering died when I tried to use it on TypeScript repo (which has 1.20 GB at the time of writing this).

Juro Oravec

2020-04-08

Very useful for gaining insight into project structure, reviewing whether the structure is suitable and finding suggestions for refactoring and restructuring.

Example: Rendered one of the projects I worked on with CodeFlower, discovered that in frontend components there was one file which was X times larger than the rest, and realised that the file actually harboured multiple functionalities and should be most likely split into individual components.

Note, however, that since CodeFlower uses D3, there's a limit to what it can render. Small- and mid-sized projects are fine. But, rendering died when I tried to use it on TypeScript repo (which has 1.20 GB at the time of writing this).