feat(world): add config resolution at runtime #2421
Conversation
alvrs
commented
Mar 13, 2024
•
alvrs
commented
- adds the runtime implementation corresponding to feat(world): add types for v2 config resolvers #2389
|
alvrs
changed the title
| @@ -2,4 +2,4 @@ export * from "./defaults"; | |||
| export * from "./storeConfig"; | |||
|
|
|||
| export * from "./experimental/resolveConfig"; | |||
| export * from "./v2/store"; | |||
| export * from "./v2"; | |||
There was a problem hiding this comment.
thoughts on a separate config entry point for now?
https://github.com/latticexyz/mud/pull/2415/files#diff-9b298d2cadfb9600e8878ee44b4064e32664a2c00322309b5cf434e75ab87f31
thinking that'll make it easier to grep for things when we inevitably move stuff around
| Object.entries(namespaces) | ||
| .map(([namespaceKey, namespace]) => { | ||
| const tables = get(namespace, "tables") ?? {}; | ||
| return Object.entries(tables).map(([tableKey, table]) => [`${namespaceKey}__${tableKey}`, table]); |
There was a problem hiding this comment.
not sure if we wanna use this here but we have resourceLabel in @latticexyz/common
| ); | ||
|
|
||
| return { | ||
| tables: resolveStoreTablesConfig({ ...(get(input, "tables") ?? {}), ...namespacedTables }, scope), |
There was a problem hiding this comment.
do we need to do any validation that there are no overlaps?
