Multi-module project structure

Open
  • Is something wrong?
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
scala
Domain
build-system

Research direction

No files, tests, or entry points are named. Start by reviewing the current project layout and the discussion linked from pull request #94; done means an agreed module breakdown and a clearly defined implementation scope.

Written by the indexing model from the issue text.

Description

Consider breaking the project into modules:

  1. Test stuff
  2. ... (TBD)
  3. ...

See https://github.com/AbsaOSS/commons/pull/94#issuecomment-1035444182

Dominant language
Scala
Stars
11
Forks
1
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 AbsaOSS/commons

All issues in AbsaOSS/commons

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.