It's quite common that people use their personal group id to release alpha versions of their project. Those temporary artifacts are sometimes selected by Scaladex as the default artifact. They should not. To fix this issue we can introduce a defaultGroupId field in the Project.Settings.
Identified Obstacles
Use the defaultGroupId field to compute the default artifact in ProjectHeader, to compute the badges, and to sort the artifacts.
Implementation Guideline
Add the defaultGroupId field in the Project.Settings
Add the default_group_id column in the project-settings table by adding a SQL migration file here and adapt the SQL requests in ProjectSettingsTable.
Add the drop down list in the edit-project.scala.html for the user to pick the default artifact.
Add the defaultGroupId field in ProjectHeader and use it to compute the default artifact
Check that it is also used to compute the badges
Expectations
The defaultGroupId should be used to compute the default artifact, the badges, and to sort the artifacts. There should be some unit tests.
Motivation
It's quite common that people use their personal group id to release alpha versions of their project. Those temporary artifacts are sometimes selected by Scaladex as the default artifact. They should not. To fix this issue we can introduce a
defaultGroupIdfield in theProject.Settings.Identified Obstacles
Use the
defaultGroupIdfield to compute the default artifact inProjectHeader, to compute the badges, and to sort the artifacts.Implementation Guideline
defaultGroupIdfield in theProject.Settingsdefault_group_idcolumn in theproject-settingstable by adding a SQL migration file here and adapt the SQL requests inProjectSettingsTable.edit-project.scala.htmlfor the user to pick the default artifact.defaultGroupIdfield inProjectHeaderand use it to compute the default artifactExpectations
The
defaultGroupIdshould be used to compute the default artifact, the badges, and to sort the artifacts. There should be some unit tests.