Skip to content

Conversation

marcelfolaron
Copy link
Contributor

stripUndefined will remove all undefined parameters from an object however that breaks the prototype chain.
AbortSignal being a native node.js object shouldn't be processed like that. It has properties that are valid if undefined.
Skipping the strip for AbortSignal fixes the issue.

Checklist (if applicable):

stripUndefined will remove all undefined parameters from an object however AbortSignal (per standard) has properties that are valid undefined. Skipping the strip for AbortSignal fixes the issue.
@MichaelDoyle
Copy link
Member

@marcelfolaron thank you!! I was banging my head against this earlier in the week.

This LGTM, but looping in @pavelgj as well.

@MichaelDoyle
Copy link
Member

MichaelDoyle commented Aug 9, 2025

@marcelfolaron would you mind doing an pnpm run format and push again? Thanks!

@marcelfolaron
Copy link
Contributor Author

marcelfolaron commented Aug 9, 2025

pnpm run format

Ah, missed that one. Pushed the updated version

I was banging my head against this earlier in the week.

This was a doozy but since I was encountering that as well it was a good way to start diving deeper and contributing :)

@pavelgj pavelgj enabled auto-merge (squash) August 10, 2025 21:11
@pavelgj pavelgj merged commit 0ab66ea into firebase:main Aug 10, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[JS] abortSignal does not work with dotprompt
3 participants