This message was deleted.
# ask-anything
s
This message was deleted.
e
you can pass dictionaries as keys in grid, but I'm unsure if this is what you're looking for:
Copy code
grid:
  some_dict:
     some_key: some_value
then, you can refer to the values in the task names:
Copy code
name: some-task-[[some_dict.some_key]]
Note: We have not tested the dot notation (
[[something.another]]
) since we never thought about that use case but my guess is that it should work since we're just passing jinja variables to render the task name. so if you have issues let me know!
j
Yeah I mean I'd rather have those configs somewhere else than env.yaml or pipeline.yaml because I have many of them
For now I just pass their filenames as params in grid - how does Ploomber compare to Hydra? 😄
I mean Hydra kinda does this, but I'd much rather have small subset of Hydra functionality in Ploomber than move from Ploomber
For starters I remember I tried using decorators to add type validation (I mean I'd load JSON from somewhere and then convert it to my config classes) and it was cumbersome
A concrete idea for implementation would be to add integration with dataclasses, something like Pydantic in FastAPI
@Eduardo thanks for being a rubber duck XD I think I'll write a proposal for this (I imagine it won't be hard but it requires understanding how ploomber calls stuff)
e
it's a bit difficult for me to understand how the API looks like since i've never used Hydra, so yeah, feel free to write an API proposal, we can work it out and then you can submit a PR. I can help navigating the different modules to understand how ploomber calls things!