isXander / isXander/YetAnotherConfigLib

Map config values (or just map option groups)

Open
#273 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I'm working on McQoy, which automatically generates config GUIs for mods that use an existing pure-java config library.

Primitives, sections, and lists all work, but I noticed there's nothing in YACL's API that can handle Map<String, T>, which I use very often in my mods for configuration over arbitrary items/tags/screens/biomes/etc.

To work around this, I'm planning to attempt to create something custom, but it'll end up using a lot of internal yacl API and might realistically be quite brittle.

With the exceedingly nice way that list groups are already designed, I reckon you'd know exactly what you're doing here - first-class support for map groups would be greatly helpful!

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 by reading YACL's existing list-group API and the surrounding configuration-group design. Compare those entry points with the Map<String, T> use case described for McQoy, then determine what first-class map groups should support and how completion can be verified through the library's existing API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.