Joshua Smithrud
Joshua Smithrud
VSCode intellisense does not seem to respect all lower-case `@inheritdoc` in tsdoc comments. It seems to only respect the camelCase `@inheritDoc`. Other tools (e.g. API-Extractor) do not seem to have...
Fills in `SharedCounter` article for fluidframework.com. Also... - cleans up some surrounding documentation and related source-code comments. - removes some empty articles that were hidden from the website, and had...
Note: this PR is not intended to be merged. This document will be added to the github wiki. This PR exists only as a means to generate feedback on the...
The tree package was generally using tabs in source-code, and spaces in other files. This has been maintained as policy in the config, but can be changed as desired.
The `bundledPackages` option is great for managing cross-package re-exports in a way that makes reasoning about the local API surface in a wholistic way. Unfortunately, the tooling currently fails in...
[api-extractor] Don't annotate items with `{@inheritDoc}` comments as "undocumented" in API reports
For API members documented with `{@inheritDoc Foo}`, the resulting generated API report marks these as `// undocumented`. This isn't true, and leads to confusion in PRs, etc. It would be...
API-Extractor offers the option (for a number of settings) to either report issues in the generated API report file, xor fail with a console error. Missing documentation is not one...
Mostly putting this up to see what people think. I personally find consistency in import ordering helpful. If we like this pattern, we could add this to the root config...
The primary point of this PR is to settle on a commonly accepted definition / purpose for this package, and to document it for future reference.
See the updated `.api.md` file for an example of the changed generated report. This model will make it substantially easier to detect breaking changes affecting our public package. This also...