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
After latest changes in package name handling (e.g. introduction of new kinds of names, some fields becoming optional) we may want to revisit name handling across the webapp. A quick summary where (some kind of) names are used:
project/versions (package name, also sorting) - visiblename currently
the primary purpose of package name here is to visually identify which package a version relates to (note that there's also a link in most cases). We're probably OK with what we use now, e.g. primarily source names for repositories and titles for other sources. However, we still very much need Add package grouping to metapackage pages repology-rs#104 to avoid duplicate entries due to different binary package names.
project/packages (package name) - visiblename currently
names no longer identify a package (and also may be quite long), so we may move them out of the panel headers, and explicitly list source package name / binary package name, but we need a consistency in how we represent them (as the real meanings are more closer to source names we use in repology-updater's NameMapper - there are titles, IDs, items, FMRIs, recipe/source/binary package names etc.) - may save this information in repository metadata
project/information (list of names) - visiblename currently
visiblenames now mean different things for different sources, so it doesn't make much sense showing them in a single list (3) - may consider removing the list completely. This would also help with a lot of i18n entries
The text was updated successfully, but these errors were encountered:
After latest changes in package name handling (e.g. introduction of new kinds of names, some fields becoming optional) we may want to revisit name handling across the webapp. A quick summary where (some kind of) names are used:
visiblename
currentlyvisiblename
currentlyvisiblename
currentlyvisiblenames
now mean different things for different sources, so it doesn't make much sense showing them in a single list (3) - may consider removing the list completely. This would also help with a lot of i18n entriesThe text was updated successfully, but these errors were encountered: