Skip to content

Conversation

@ehughsbaird
Copy link
Contributor

Summary

Infrastructure "Allow specifying variants for brewing and compost results"

Purpose of change

Fixes #83584

Describe the solution

Replace itype with pair<itype, string>. Set the variant on creation. Add a reader to handle the format.

Testing

Add an item with a variant to brewing results.

Additional context

nname is problematic for variants and I don't know how to handle it.

@github-actions github-actions bot added <Documentation> Design documents, internal info, guides and help. [C++] Changes (can be) made in C++. Previously named `Code` [Markdown] Markdown issues and PRs Code: Infrastructure / Style / Static Analysis Code internal infrastructure and style astyled astyled PR, label is assigned by github actions json-styled JSON lint passed, label assigned by github actions labels Nov 5, 2025
@RenechCDDA
Copy link
Member

I realize this is not the way your PR is going, and I am not trying to tell you it should, but...

Have you considered the idea of moving to a recipe-based system like milling?

Recipes already have support for producing selected variants.

@ehughsbaird
Copy link
Contributor Author

It seems like milling produces single outputs, whereas brewing typically has multiple outputs. Brewable items are also already crafted, with recipes involving heating, which a recipe in this context could not do.

I am not sure that is as appropriate to apply here.

It would probably be nicer to use a struct instead of a pair here, but
not that much.
@github-actions github-actions bot added the BasicBuildPassed This PR builds correctly, label assigned by github actions label Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

astyled astyled PR, label is assigned by github actions BasicBuildPassed This PR builds correctly, label assigned by github actions [C++] Changes (can be) made in C++. Previously named `Code` Code: Infrastructure / Style / Static Analysis Code internal infrastructure and style <Documentation> Design documents, internal info, guides and help. json-styled JSON lint passed, label assigned by github actions [Markdown] Markdown issues and PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ferment results giving variants

2 participants