jsr icon indicating copy to clipboard operation
jsr copied to clipboard

Newly published packages show a blank "Works with" in the header.

Open donjo opened this issue 1 year ago • 0 comments

Screenshot 2024-04-24 at 10 01 38 AM

Right now when you first publish a package the runtime compatibility options are unset so the "works with" field in the package header is blank. If you go into settings it looks like they are all set to "unknown compatibility", however, the UI doesn't reflect that until you hit save for the first time. I would suggest one of the following options:

  1. New packages are set to "compatibility unknown" upon publish which would render some content in the "Works with" section of the package header and the form fields on the settings page would be correct.

or (if we want compatibility definition to be fully opt-in)

  1. The form fields on the settings page are set to an empty state. The "works with" section of the package header is not visibility unless at least 1 runtime compatibility (even unknown compatibility) is defined.

donjo avatar Apr 24 '24 14:04 donjo