Allow non-strings in @tag(...) about hamilton HOT 5 CLOSED

[...] that match tags with simple =, in, not =, not in type operations.

this was exactly where I was going with this, works for me!

from hamilton.

Agreed that we should allow for some structure here. I think we have two choices:

1. Allow any arbitrary json here
2. Allow some specific structure that has semantic meaning.

I'm going to recommend (2). In this case:

• strings assign a value to the tag
• lists assign multiple values to the tag

Then we have a query system (suggested in here) that allows you to query for nodes that match tags. With simple =, in, not =, not in type operations. The driver maintains a list and can do the queries for you. I don't really foresee the need for anything more complex than these operations, which work nicely with the list suggested here and match the common configuration patterns... @config.when, @config.when_in, etc...

from hamilton.

also - #293.

from hamilton.

Otherwise I think lists of strings seem to be fine. Can't seem to recall why we didn't do this in the first place.

The other -- nested dicts can already be done with the namespacing/dot stuff.

@tag(**{'my.tag': 'tag_value'})
       def my_function(...) -> ...:

from hamilton.

@kzk2000 want to take #622 for a spin?

You should be able to do what you asked for.

from hamilton.