This change points the api-extractor to the di and context export paths and adds this generated documentation to the documentation site.
🎫 Issues
Resolves #6090
👩💻 Reviewer Notes
This is was a little fiddly as the api-extractor does not export export paths, additionally the way the api-documentor works assumes a single entry path. This is why if any additions need to be made to expose more export paths, we will need to edit 3 different files to get the documentation to show up on the documentation website.
✅ Checklist
General
[x] I have included a change request file using $ yarn change
[ ] I have added tests for my changes.
[x] I have tested my changes.
[x] I have updated the project documentation to reflect my changes.
[x] I have read the CONTRIBUTING documentation and followed the standards for this project.
Pull Request
📖 Description
This change points the
api-extractorto thediandcontextexport paths and adds this generated documentation to the documentation site.🎫 Issues
Resolves #6090
👩💻 Reviewer Notes
This is was a little fiddly as the
api-extractordoes not export export paths, additionally the way theapi-documentorworks assumes a single entry path. This is why if any additions need to be made to expose more export paths, we will need to edit 3 different files to get the documentation to show up on the documentation website.✅ Checklist
General
$ yarn change