chore(angular): recreate angular test app

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally for affected output targets
• Tests (npm test) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

The Angular test app is very outdated. It has opinionated tests for components that act similar to Ionic Framework, but are beyond the scope for this integration.

What is the new behavior?

• Updates the Angular test app (v16) with a new project generated from the Angular CLI
• Sets up a basic structure for testing the generated framework wrappers
  • Only testing the my-button to start (we can fill in new tests as we identify areas that we need coverage)
• Stops tracking auto-generated files to source control

Does this introduce a breaking change?

• Yes
• No

Other information

Will submit future PRs to upgrade the example Stencil lib to v3.

[rwaskiewicz]

I'm gonna tag @tanner-reits to give a more thorough Angular review. I had a few high level questions, but not blocking on them

[rwaskiewicz]

I may be missing something, but do we need the Vue-related changes in this file in this PR?

[sean-perkins]

This is an autogenerated file. When previous PRs changed the vue output target, they did not run npm run build from the example Stencil project, so the output targets output wasn't updated.

When updating the other framework example apps, these files will be removed from source control.

[rwaskiewicz]

I take it that these tests (in __tests__) are the ones mentioned in the PR summary?

It has opinionated tests for components that act similar to Ionic Framework, but are beyond the scope for this integration.

Does that mean that we don't plan on backfilling/adding tests to the new test app? Or that those will just be coming in a future PR?

EDIT: Ah, maybe https://github.com/ionic-team/stencil-ds-output-targets/pull/358/files#diff-1e2b03b89f374dd1898b69732368234ce6b7b290a8b6dcd58b3bf10166b192ac is the replacement or sorts?

[sean-perkins]

Correct on the referenced test file. Future PRs will fill in expected integrations we want to account for with the generated proxies. Currently we have too complex of components and tests, than are necessary for what the output targets are responsible for. This was likely because we just copied the component structure from Ionic Framework.

We can probably set up a nightly CI against Ionic Framework if we wanted that.

[tanner-reits]

All looks good from the Angular side 👍

[liamdebeasi]

Nothing big stuck out to me. Had similar questions as Ryan, but those were addressed with your comments.

[christian-bromann]

Closing in favor of #542