isXander / isXander/YetAnotherConfigLib

Allow subclasses for @AutoGen

Open
#141 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
155
Forks
68
PR merge metrics
No merged PRs in 30d

Description

I suggest adding a new @AutoGen(passthrough = true) option specifically to enable this kind of thing:

@SerialEntry
@AutoGen(category = CHEATS, passthrough = true)
 // this means that the field won't be converted to an option
 // instead the fields of this object will 
public Cheats cheats = new Cheats();

public static final class Cheats {
    @SerialEntry
    @TickBox
    @AutoGen // All of the fields generated under the category CHEATS
    // The category field has to be optional and have a usage contract instead 
    public boolean expendWandChargeInSurvival = true;
}

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

No source file or test is named. Start by tracing how the @AutoGen annotation handles category values and generated fields, then compare that behavior with the nested Cheats example. Done means a passthrough option can generate nested fields under the parent category without converting the parent field itself into an option, with the category field remaining optional.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.