Thank you for your pull request! Please provide the following information.
Change Description:
Customer reporter linter error on yo office output. Turns out this only shows up after regenerating the lock file. Adding a child property to HeroListProps interface definition fixes this.
Do these changes impact any npm scripts commands (in package.json)? (e.g., running 'npm run start')
No.
Do these changes impact VS Code debugging options (launch.json)?
No.
Do these changes impact template output? (e.g., add/remove file, update file location, update file contents)
No.
Thank you for your pull request! Please provide the following information.
Change Description: Customer reporter linter error on yo office output. Turns out this only shows up after regenerating the lock file. Adding a child property to HeroListProps interface definition fixes this.
Do these changes impact any npm scripts commands (in package.json)? (e.g., running 'npm run start') No.
Do these changes impact VS Code debugging options (launch.json)? No.
Do these changes impact template output? (e.g., add/remove file, update file location, update file contents) No.
Do these changes impact documentation? (e.g., a tutorial on https://docs.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins) No.
If you answered yes to any of these please do the following:
Validation/testing performed: Ran automated test and ran linter.