Closed sjd78 closed 5 months ago
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
Note: Until language discovery is working consistently, we can manually tag a language to an application for testing purposes.
The application Analysis
fields used to correlated to task by addon. This needs to be updated to correlate by kind == "analyzer" (when not blank) else fallback on addon == "analyzer". The fallback is needed to correlate tasks created in previous releases.
Summary
With the addition of automatic language discovery, the analysis wizard target selection step needs to be enhanced.
Enhancement references:
Requirements
Base requirements:
TaskGroup.Addon: analyzer
needs to be replaced withTaskGroup.Kind: analyzer
Details on changes to the language selection box:
Provider
field of the fetched targets.Details on changes to the target cards:
HUB enhancements that may be needed:
None identified initially. Target data is already available. Tag category of "Language" is provided in the seed values. Applications already have their tag data provided.
Screen shots and mockups
Current State
Future State
(the only real difference will be he constant language/provider tag on the cards)