chore: implicityAny by default and update blueprints

[cironunes]

Closes #107

[filipesilva]

I think you forgot to change tsconfig.json to have "noImplicitAny": true,.

Other than that, it looks good.

[Brocco]

@filipesilva We don't want to enable noImplicityAny, only have the blueprints support it being turned on without causing any issue. If we were to turn it on then it would force anyone using the CLI to write code to comply with that setting, which is something we don't want to do.

[filipesilva]

Got it. Then this one looks ready to merge for me.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

[hansl]

In order to close #107, we need to consider having noImplicitAny for our e2e tests. It seems like you're not enabling it anywhere (might have missed it).

[cironunes]

@hansl this is just updating the blueprints, we can address having the config for our e2e tests in a separated PR. BTW, closing this in favor of #150

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}