Skip to content

build: some public API docs missing descriptions #22482

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

Merged

Conversation

crisbeto
Copy link
Member

Fixes that some inherited class members didn't have descriptions in the generated docs. The problem seems to be that we were using the description field, whereas the text was in the content field. I don't have the context behind why we were using description, but the field doesn't exist in Dgeni's typings and content seems to work in all the cases I tried.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround merge safe target: patch This PR is targeted for the next patch release labels Apr 14, 2021
@crisbeto crisbeto requested a review from devversion April 14, 2021 19:47
@crisbeto crisbeto requested a review from a team as a code owner April 14, 2021 19:47
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 14, 2021
Fixes that some inherited class members didn't have descriptions in the generated docs. The problem seems to be that we were using the `description` field, whereas the text was in the `content` field. I don't have the context behind why we were using `description`, but the field doesn't exist in Dgeni's typings and `content` seems to work in all the cases I tried.
@crisbeto crisbeto force-pushed the 22128/api-docs-missing-description branch from a09f4af to 0bc86d0 Compare April 14, 2021 20:00
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 No idea where the description came from. Maybe a leftover from our initial dgeni setup that could have set the property.

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Apr 16, 2021
@wagnermaciel wagnermaciel merged commit c2d5b7c into angular:master Apr 19, 2021
wagnermaciel pushed a commit that referenced this pull request Apr 19, 2021
Fixes that some inherited class members didn't have descriptions in the generated docs. The problem seems to be that we were using the `description` field, whereas the text was in the `content` field. I don't have the context behind why we were using `description`, but the field doesn't exist in Dgeni's typings and `content` seems to work in all the cases I tried.

(cherry picked from commit c2d5b7c)
wagnermaciel pushed a commit that referenced this pull request Apr 19, 2021
Fixes that some inherited class members didn't have descriptions in the generated docs. The problem seems to be that we were using the `description` field, whereas the text was in the `content` field. I don't have the context behind why we were using `description`, but the field doesn't exist in Dgeni's typings and `content` seems to work in all the cases I tried.

(cherry picked from commit c2d5b7c)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants