Skip to content

Think about using tags for more things #86

@quintesse

Description

@quintesse

Some ideas:

  • Allow user tags. Imagine you're linking to a specific JDK build, for example a Valhalla one, and you want to mark it as being special. You could imagine giving it a "valhalla" tag somehow. That way if you have several of them you could say: "27,valhalla" to indicate you want to use Java 27, but not just any one, you want one that has the "valhalla" tag.
  • Set vendors as tags instead of a special "vendors" field. The pro is that it's easy, we'd be re-using an existing feature instead of introducing specialized fields. The con is that it might either conflict with user tags or it might be ambiguous . (If trying to install "26,temirun" is that because of a typo in a vendor name or is it some other issue? This might be resolved somewhat by using compound tag names, eg: "vendor=temurin", but not sure if that is a can of worms)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions