Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Discussion: accept `pantry.toml` as the pantry file name (keeping `pantry.conf`)

Abierto
  • ¿Algo no está bien?
#689 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
cli

Línea de trabajo

Start with crates/core/src/context.rs and the pantry edit path at crates/core/src/pantry/mod.rs:1142; inspect how Context::discover and Context::search find pantry files. The proposal is still under discussion, with compatibility questions about other apps and older CookCLI versions unresolved, so first determine whether the change is agreed before attempting implementation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: pantry feature request needs discussion

This is a proposal for discussion, not a decided change. Comments are welcome, especially from anyone who maintains another app that reads the pantry file.

Background

A recipe folder can hold two hand-written config files side by side, in two different formats:

File Format Comments
config/aisle.conf Cooklang's own format ([aisle], then name | synonym) //
config/pantry.conf TOML #

Both end in .conf, so nothing tells you which one is which. #687 (reported on Discord) is the result: someone wrote # comments in aisle.conf, the way pantry.conf beside it takes them, and they became ingredients. #688 now warns about those lines, but the cause is still there. The same confusion works in reverse: // note or -- note in pantry.conf is a TOML error, and the web shopping list then ignores the whole pantry.

The spec's conventions.md says the pantry file is TOML, but it doesn't name the file. pantry.conf is a CookCLI convention.

Proposal

Accept pantry.toml as the pantry file's name, and keep reading pantry.conf:

  1. Look for pantry.toml first, then pantry.conf, in ./config/ and in the global config dir (COOK_CONFIG_DIR, ~/.config/cook/, …). All lookups go through Context::discover / Context::search in crates/core/src/context.rs, so this is mostly one place.
  2. If both exist, use pantry.toml. cook doctor pantry and the /pantry page say that pantry.conf is being ignored.
  3. Edits (the CLI and the /pantry page) go back to the file that was read, whatever its name.
  4. When there is no pantry yet, the first edit creates config/pantry.toml instead of config/pantry.conf (crates/core/src/pantry/mod.rs:1142). The exception is if another app turns out to look for pantry.conf by name (question 1): then new pantries stay pantry.conf until those apps read both names. Otherwise, new users would still get the two .conf files side by side.
  5. Docs, README and help texts say "pantry.toml (or pantry.conf)".

aisle.conf keeps its name and its format. With pantry.toml next to it, the different extensions show that the two files have different formats.

Questions

  1. Does anything else look for config/pantry.conf by name? For example the Cook mobile apps, cook.md, or the sync service. If one does and a user renames the file, that app loses the pantry without saying why. This is the main question; if the answer is yes, those apps need to read pantry.toml too before CookCLI creates it.
  2. Is it worth it? About 60 files on main mention pantry.conf (tests, docs, the 9 locales, core, server). The alternative is to keep the name and rely on documentation plus the #688-style warnings.
  3. Should the spec name the files? conventions.md could say "pantry.toml (formerly pantry.conf)", so that every app agrees.
  4. When should new pantries become pantry.toml? Right away, or after one release that reads both names, so that an older cook on the same folder still finds the pantry?

Not part of this proposal: changing the aisle.conf format. That needs the spec and cooklang-rs, and was option 3 in #687.

Lenguaje dominante
Rust
Estrellas
1.4k
Forks
120
Merge medio
1 d 22 h
PR fusionados (30 d)
128

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cooklang/cookcli

Todos los issues de cooklang/cookcli

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.