Walter Oggioni 326afacedb improved interactive shell flow lookup logic (#6271) ... the current logic when a user type ``` flow start SomeFlow ``` is to search for the string `SomeFlow` in all registered flow names, if there is at exactly flow that ends with that string, it will be selected, if there is more than one, the first in aphabetical order will be selected. If there are multiple flows that contains the string but no one that ends with it, it is considered ambiguous, if there is exactly one containing the string it is instead selected (it doesn't matter whether it ends or not with it). All other cases are considered errors. The goal of this change is to address the case where the node contains ``` net.corda.cordappp.AnotherSomeFlow net.corda.cordappp.ImprovedSomeFlow net.corda.cordappp.SomeFlow ``` typing ``` flow start SomeFlow ``` currently results in running `net.corda.cordappp.AnotherSomeFlow` because it comes first in alphabetical order, while `net.corda.cordappp.SomeFlow` is a better matches because the input substring matches a bigger portion of the full flow name		2020-05-21 09:27:13 +01:00
..
src	improved interactive shell flow lookup logic (#6271)	2020-05-21 09:27:13 +01:00
build.gradle	https://r3-cev.atlassian.net/browse/ENT-3829 (#5763)	2019-12-03 10:28:00 +00:00