Make the project structure more generic

Created on 12 June 2024, over 1 year ago

I am working on a plugin to integrate with Gitlab. I think the "Projet" object is very opinionated and tied to d.o project structure. It would be great to not display the information on the frontend if no value is given. For example, "By undefined" should not be displayed if Author is not set.

I think the plugins will mainly be used to connect to private sources and so many information may not be available nor interesting in that situation.

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡«πŸ‡·France vbouchet

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @vbouchet
  • Status changed to Postponed: needs info 11 months ago
  • πŸ‡ΊπŸ‡ΈUnited States chrisfromredfin Portland, Maine

    We set out to be opinionated about what backend sources need to provide, and that was fairly intentional. We also have recently removed quite a few things of cruft from the Project object. I'd love to know specifically which ones you aren't able to provide and why.

    For example, though we require "popularity" / number of installs, ex.g., we don't show if it's 0.

    There may be workarounds that are smaller in scope than "change the API," so I'd love to know more specifics.

  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    I would agree that we need more specifics here.

    The Project object is now a beta-level part of our API, which means that it must maintain backwards compatibility. If we want to add properties to it, or alter existing properties, we should probably do that in a series of individual issues that consider the use cases and ramifications.

    Removing the tags here since we are well beyond alpha at this point, and since the Project object is stable API, this is not going to block MVP.

Production build 0.71.5 2024