Feedback

[offworldcoder]

Although I've pointed out a few nice to haves and issues, the overall look and feel is really nice. It's the closest I've found to what I was originally looking for.

[YoannBuch]

Thank you! It's always great to get feedback. It's the best way to keep us moving and make Flow better.

Why were you looking for a solution like Flow? Did you have a specific use case in mind? Like learning about a new code base? Finding the root cause of a bug? Something else?

[offworldcoder]

Hi, I was trying to identify places in our current tests to place specific check. I was having trouble working out where to put them so wanted a call graph diagram to help me work it out. I still haven't worked out where to put them. I'm not sure if you plugin was what I was actually after but it started to help. As the visualisations doesn't show the order of the calls it got quite confused. At the moment I've stepped away from our issue, will come back to it later. Thanks, Lee

…

________________________________ From: YoannBuch <[email protected]> Sent: 28 June 2017 18:01 To: findtheflow/Feedback Cc: offworldcoder; Author Subject: Re: [findtheflow/Feedback] Feedback (#19) Thank you! It's always great to get feedback. It's the best way to keep us moving and make Flow better. Why were you looking for a solution like Flow? Did you have a specific use case in mind? Like learning about a new code base? Finding the root cause of a bug? Something else? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#19 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFm7q5XPwCFT7ZxGHs4Uu7OZYR96F8sFks5sIpTegaJpZM4OGukJ>.

[YoannBuch]

Thanks for the details.

It's true that the call graph gives no information about the order of calls, as we've discussed in a different issue. But I wanted to stress that the other visualisation, the call stack, shows the order of calls.