tree 4254e52e9faad9e3ec4483e74c3a8ce9599126e6
parent 55b50fe9a1434ca535b7778e972dc8b47b48c72a
author Manu Sridharan <msridhar@gmail.com> 1542157338 -0800
committer GitHub <noreply@github.com> 1542157338 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJb63QaCRBK7hj4Ov3rIwAAdHIIACKaHBfzJqMDMtxDiDp0B5zs
 qqa+tevKNUP1jN617NeCTe+5RtmLWMxbVHqZn5QLIbzqcLGtFcNFjnlzHvK7zNUD
 +4bVEIxgtaT99S9V8cjlL6vfkCjGMHuo086J9p9LNxXJwAyI1RyW0Rgay1k4857e
 qh+PXp39US4hG5tpvFktXiOPJeR/aofJJYXVzQ4dfUkWc79YcxkR0Aul0Hkf1aDZ
 KGsWOX6I6z3jU6/AhLb/slJQOBpS3OogGzgqJipQpw3pjRQpYzO4SDK1d+sFrxek
 5gktsF4OsQokdNUPO7ZxyfxXISbC8T1MCqX/ZEOzM9BSm9yHUlG/x1XJMI30kGc=
 =nOkV
 -----END PGP SIGNATURE-----
 

Handle interaction between AcknowledgeRestrictiveAnnotations and TreatGeneratedAsUnannotated (#254)

If both the `TreatGeneratedAsUnannotated` and `AcknowledgeRestrictiveAnnotations` are set, previously we would still use any `@Nullable` annotations in generated code when checking clients.  This PR implements the desired behavior, which is to ignore those `@Nullable` annotations.

This points to a deeper issue in our terminology (kind of weird to use annotations from "unannotated" code) and config options.  But fully addressing that is outside the scope of this PR.