Skip to content

UI support for conan revisions and package reference

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

This is a separate issue about UI support for conan revisions based on #333033 (closed)

🌈 Support revisions on UI

First of all, I'm not a UI person. 😸 Please read this section with the grain of salt.

Currently, we store package_reference, recipe_revision and package_revision in the database, that can be propagated to UI using GraphQL. I'm wondering if we could use that information to visually group files on the UI 🤔. I could see two options:

  1. Display files as a directory/files tree.
  2. Group files into sections with sub-titles as Recipe revision #ce79982197e975775a58d5537fa7dee6, Package revision #e141375a352e73f359bcfdb05fa4930d, Package reference #f7d20a1ee5f03368876d6237802a196d214489dd or maybe even more complex RREV #ce79982197e975775a58d5537fa7dee6 PREV #e141375a352e73f359bcfdb05fa4930d, where RREV stays for recipe revision and PREV for package revision.

It seems that (1.) may be quite a lot of frontend work and, perhaps, we should explore (2.) or other alternatives.

\cc @dmeshcharakou As it is the person that wrote this text 😄

Edited by 🤖 GitLab Bot 🤖