Skip to content

build: docs incorrectly outputting function parameters with object literal type #29471

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
merged 1 commit into from
Jul 23, 2024

Conversation

crisbeto
Copy link
Member

We were extracting the type of a function parameter by splitting on : and taking the second item. The problem is that if the type is an object literal, it'll have more than one colon in its text.

These changes fix the issue by only looking for the first colon and extracting the name based on it.

…teral type

We were extracting the type of a function parameter by splitting on `:` and taking the second item. The problem is that if the type is an object literal, it'll have more than one colon in its text.

These changes fix the issue by only looking for the first colon and extracting the name based on it.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jul 23, 2024
@crisbeto crisbeto requested a review from a team as a code owner July 23, 2024 07:02
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Jul 23, 2024
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jul 23, 2024
@crisbeto crisbeto merged commit 315ebf1 into angular:main Jul 23, 2024
27 checks passed
crisbeto added a commit that referenced this pull request Jul 23, 2024
…teral type (#29471)

We were extracting the type of a function parameter by splitting on `:` and taking the second item. The problem is that if the type is an object literal, it'll have more than one colon in its text.

These changes fix the issue by only looking for the first colon and extracting the name based on it.

(cherry picked from commit 315ebf1)
@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 Aug 23, 2024
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 area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants