Port Detection Logic Optimizations

/kind epic

Which area this feature is related to?

/area cli /area api /area library /area documentation

Which functionality do you think we should add?

A group of new port detection logic optimizations should be introduced for alizer. Moreover:

Alizer should follow specific paths for port detection to each framework detector.
Define combining strategies and "no port detection" strategy for component analysis.

Why is this needed? Is your feature request related to a problem? A group of optimizations should be made to alizer in order to improve the performance of the tool. As already have seen in #208 alizer was spending too much time analyzing dirs not related to the project directly (e.g vendor or node_module dirs).

A second iteration should be made for this issue, as already have reported to #209.

Describe the solution you'd like

As a fair amount of changes will be introduced to alizer's logic a proposal should be added under docs/proposals.

Other than that, we could introduce 2 potential optimizations for this issue:

Apply port detection for specific paths As a first step for better performance during port detection we can define certain paths and files for port detection and each detector. So, upon port detection process the detector will only check for configured ports inside these paths

Implement Combined and No Strategy Options Currently, upon component command we have the port-detection arg which specifies the port-detection strategy. We can ensure that we include sufficient information to our docs regarding that someone can combine these options and we should introduce a none value.

redhat-developer / alizer