PaperMC / PaperMC/paperweight

Implement arbitrary patch set support

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

Nobody has claimed this yet.

hopefully type: feature
Dominant language
Kotlin
Stars
317
Forks
76
Avg merge
1d 12h
Merged PRs (30d)
5

Description

Patch sets would have properties which define how they are applied and what they are etc.

Example config in Kotlin I came up with on the fly:

patchSets {
    "base" {
        "decomp"()
        "impl" {
            patchType = PatchType.FILE
        }
    }
    "feature" {
        "async" {
            "some-thing"()
            "other-thing"()
        }
    }
}

A language designed for configuration like hocon (or other options) may be better and cleaner. There may be other options and properties for patch sets as well.

This is just for book keeping so I don't forget about building out this functionality.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the Kotlin configuration example in the issue and compare its proposed patch-set properties with the discussion of HOCON or other configuration options. No repository files, tests, entry points, or acceptance criteria are named, so the design and definition of done need to be established before implementation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.