#Have you thought about "defaultPath"?

1 messages · Page 1 of 1 (latest)

analog mango
#

not yet, I need to look at this one as well as ignore that is also not yet handled for instance

wraith cliff
#

It's ok that it's not supported yet, but it pays to think now about where those annoations will fit in.

#

Is it valid to have @Optional(defaultValue="foo") or @Optional(defaultPath="bar"), but not both? Is it possible for you to know whether defaultPath is being used on a dagger.Directory versus other types?

#

I can imagine a separate @Ignore(...) so that's ok.

analog mango
#

Is it valid to have @Optional(defaultValue="foo") or @Optional(defaultPath="bar"), but not both?
I'd say not from the user's perspective. I mean it will not be possible to flag it for instance in the user's IDE.
But when we will parse the annotation, at compile time, yes we can handle them the way we want. And yes, I have access to the annotated type, so I can have a rule saying if it's a dagger.Directory defaultValue must not be set but defaultPath can.