Closed Mossaka closed 3 weeks ago
Thanks! To your question: originally, there was a sketch to use value imports to import configuration values, with 1 value import per individual configuration value, allowing the names of required configuration values to be known declaratively, allowing various DX/security/perf improvements. But that was a much bigger lift (for the tooling and runtime), so we instead prioritized adding a more-dynamic (runtime) configuration interface (which we'd need in any case, since sometimes you just don't know AOT what configuration you need), hence the name of the repo. Whatever the history, renaming the repo to wasi-config to match wasi:config
makes sense to me. Eventually, I'd like to return to the declarative value-import approach, we could just add that to this same repo (alongside wasi:config/store
).
Could you please take a look? @thomastaylor312
And I am all good with a repo rename
It renames:
runtime
->store
config-error
->error
and
delete the hand-written
config.md
in preference of the generatedimports.md
doc. Closes #13question: I remember we briefly discussed this but I forgot about the rationals behind the subtle difference between the proposal name "wasi-runtime-config" and the actual WIT package name "wasi:config", what are the reasons? Could we rename this repo to "wasi-config" but keeps runtime configuration as an option in the README? @thomastaylor312 @lukewagner