Cross-scala versions conflict on sub-projects

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi, scala
Domain
build-system

Research direction

Start with the related OpenAPITools issue 9856, then trace how Scala subprojects are generated and where default Scala and cross-Scala versions are configured. Done means an isScalaModule option can prevent those defaults so they remain managed by the root project, with coverage for the generated-project behavior.

Written by the indexing model from the issue text.

Description

Related to https://github.com/OpenAPITools/openapi-generator/issues/9856,

When generated project defined as scala subproject we might want to provide additional parameter isScalaModule to prevent define default values for scala and cross-scala versions as it supposed to be managed on root project

Dominant language
Scala
Stars
43
Forks
44
Avg merge
2d 1h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenAPITools/sbt-openapi-generator

All issues in OpenAPITools/sbt-openapi-generator

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.