attribute resolver script

[Cantor, Scott]

> > To be fair, the wiki page on MappedAttributeDefinition does say “many-to-
> > many”. That didn’t sink in on first read.
> 
> To me, given each value of input, I would think you'd get *a* mapped or
> default value out (or nothing if there's no match and no pass through). If
> that's not what it does, then I don't know why or why that's useful.

So, I guess maybe the problem is I *do* understand it, but don't understand what other people are expecting it to do, so I get confused when people ask questions about it. It certainly seems from the code like it does what I described, and I guess that's what you mean by many to many. There's an output (potentially) for each input, and that's what I would expect.

It couldn't do anything else since it wouldn't make sense. If you matched X and Y and both were in the input set, how could it know what to output if the expectation was only a single value?

Per Mike's point, the docs may be off, but it definitely does add the default value in if the inputs are empty. Don't know if that's a change or not. Does seem a bit weird, but oh well.

-- Scott