Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add api-extractor generated docs for di and context export paths #6979

Merged
merged 8 commits into from
Aug 1, 2024

Conversation

janechu
Copy link
Collaborator

@janechu janechu commented Jun 7, 2024

Pull Request

📖 Description

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

  • I have included a change request file using $ yarn change
  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

janechu added a commit that referenced this pull request Jun 13, 2024
# Pull Request

## 📖 Description

This change fills out the dependency injection documentation with some examples, for regular JavaScript and dependency injection for web components.

## 👩‍💻 Reviewer Notes

The document does not contain an exhaustive list of all the capabilities of our current dependency injection utilities. We will be adding generated API documentation for this, and all other specific exports for users to refer to. See #6979 

## ✅ Checklist

### General

<!--- Review the list and put an x in the boxes that apply. -->

- [ ] 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](https://github.com/microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://github.com/microsoft/fast/blob/master/CODE_OF_CONDUCT.md#our-standards) for this project.

## ⏭ Next Steps

- Add `api-extractor` generated documentation for all named exports.
@janechu janechu force-pushed the users/janechu/add-api-extractor-to-all-exports branch from f76306d to f4373e5 Compare July 2, 2024 19:04
@janechu janechu merged commit 97bf709 into master Aug 1, 2024
7 checks passed
@janechu janechu deleted the users/janechu/add-api-extractor-to-all-exports branch August 1, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs: develop API documentation strategy for package 'exports' fields
3 participants