You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
The description field of hawkbit artifacts is currently used by the Kuksa appstore to save user-IDs. #113 mentions the description field in connection with consent management. I.e. the description field is used for a potentially growing number of aspects besides a (human-readable) description.
Following clean-code practices, it is beneficial to use dedicated fields with appropriate names for the other aspects, e.g. authorization. If hawkbit does not premit arbitrary meta-data for artifacts in the hawkbit version that we use, metadata might be available in a more recent version or we could request this feature from the hawkbit team.
The text was updated successfully, but these errors were encountered:
ghost
changed the title
[Appstore] Clean code for the description field
[Appstore] Clean code description field
Sep 23, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
description
field of hawkbit artifacts is currently used by the Kuksa appstore to save user-IDs. #113 mentions the description field in connection with consent management. I.e. thedescription
field is used for a potentially growing number of aspects besides a (human-readable) description.Following clean-code practices, it is beneficial to use dedicated fields with appropriate names for the other aspects, e.g. authorization. If hawkbit does not premit arbitrary meta-data for artifacts in the hawkbit version that we use, metadata might be available in a more recent version or we could request this feature from the hawkbit team.
The text was updated successfully, but these errors were encountered: