You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we must manually create the supportedScalaVersions and supportedJavaVersions settings in sbt when generating CI tests. However, this approach becomes tedious and error-prone, particularly as the number of submodules increases. To address this issue, we need to develop a way to automatically generate these settings by iterating over each project and extracting its settings.
However, we cannot simply use a regular map or flatMap function to iterate over the submodules. Instead, we must leverage internal sbt functionalities and macros to achieve this. The current workaround of manually creating these settings is not a sustainable solution, and we should seek to automate this process for improved efficiency and maintainability.
The text was updated successfully, but these errors were encountered:
Currently, when we want to generate CI Tests, we need to create these two sbt settings manually:
supportedScalaVersions
supportedJavaVersions
An example of
supportedScalaVersions
:Currently, we must manually create the
supportedScalaVersions
andsupportedJavaVersions
settings in sbt when generating CI tests. However, this approach becomes tedious and error-prone, particularly as the number of submodules increases. To address this issue, we need to develop a way to automatically generate these settings by iterating over each project and extracting its settings.However, we cannot simply use a regular map or flatMap function to iterate over the submodules. Instead, we must leverage internal sbt functionalities and macros to achieve this. The current workaround of manually creating these settings is not a sustainable solution, and we should seek to automate this process for improved efficiency and maintainability.
The text was updated successfully, but these errors were encountered: