-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the assignment of Keywords in DejaCode more flexible #48
Labels
Milestone
Comments
DennisClark
added
enhancement
New feature or request
integration
Integration with other applications
labels
Feb 12, 2024
tdruez
added a commit
that referenced
this issue
Feb 19, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
Feb 19, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 13, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 13, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 13, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
@DennisClark Keywords validation was relaxed to accept any values. The existing values in the database are use for the autocompelte suggestion. |
@tdruez wonderful, thanks. Confirmed in Staging Starship. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We should use the ComponentKeyword as suggestions in the keyword autocomplete fields and remove the validation to allow any keywords values.
In DejaCode, at the moment, only keywords existing as ComponentKeyword in the Dataspace are allowed. This approach is not compatible with automatically adding arbitrary keywords from Scan results or other integration processes.
Background: Scan results from SCTK returns keywords such as:
The text was updated successfully, but these errors were encountered: