@Deprecated to work like @Ignore

[phillip-kruger]

Add test cases for @deprecated and make sure that it can work the same as @ignore

Meaning that if placed on the field, both Input and Output is deprecated, however putting it on the getter of setter only the input or output is deprecated. (Same as @ignore)

[andymc12]

This was considered a stretch goal for 1.0, but we're past the original cutoff date for 1.0, so I'm moving this to 1.1. We will need to remove the existing @Deprecated API annotation and spec text for 1.0 - I'll open a separate issue or that.

[phillip-kruger]

Can this now move back to 1.0 ?

[andymc12]

I'd say that we should leave it at 1.1 until we have a pull request ready to go before the 1.0 deadline (I reset that to be December 2).

[t1]

Actually, I think things annotated as @Deprecated should not be simply ignored, but get the @deprecated directive instead.

[phillip-kruger]

Yes, that is the idea, the "work like ignore" just means that we allow it on get and set and field, so it applies to output, input or both. We will also have our own annotation (that can take a reason) but will also support the java one.

[t1]

The new annotation could be implemented as a custom directive #344.