I had a few assets with this kind of definition wh...
# dagster-feedback
I had a few assets with this kind of definition which stopped working after updating from 1.3.x to 1.4.2 @asset(non_argument_deps={"my_asset_prefix/my_asset_name"}) They started hitting this error:
Copy code
dagster._core.errors.DagsterInvalidDefinitionError: "my_asset_prefix/my_asset_name" is not a valid name in Dagster. Names must be in regex ^[A-Za-z0-9_]+$
Was this style of string path with / removed? It didn't work in the deps[...] equivalent either, needed to rewrite to construct an AssetKey like
instead. Not a big deal for me, just sharing in case it was unintentional.
thanks for reporting this - we're looking into it
You're welcome. It's actually not in the docs for how to handle deps, just something I happened to notice worked in other contexts, so guessing it's not that common for people to use them this way. I like this shorter form with strings with / for path levels instead of the more verbose AssetKey((...)) - maybe after it's working again, can add that in the examples