Skip to content

Conversation

mydea
Copy link
Member

@mydea mydea commented Jul 17, 2025

This adds a lint rule to avoid usage of Object.assign (we already have similar rules for other things that are not polyfilled). We can just use object spread instead, which is polyfilled.

Fixes #16970

@mydea mydea requested review from Lms24 and andreiborza July 17, 2025 10:01
@mydea mydea self-assigned this Jul 17, 2025
cursor[bot]

This comment was marked as outdated.

@mydea mydea changed the title fix(v7/cdn): Polyfill Object.assign for ES5 fix(v7/cdn): Stop using Object.assign to be ES5 compatible Jul 17, 2025
cursor[bot]

This comment was marked as outdated.

@mydea mydea closed this Jul 17, 2025
@mydea mydea reopened this Jul 17, 2025
cursor[bot]

This comment was marked as outdated.

@mydea mydea force-pushed the fn/polyfill-object-assign branch from 0b76921 to ccf3153 Compare July 18, 2025 06:43
@mydea mydea closed this Jul 18, 2025
@mydea mydea deleted the fn/polyfill-object-assign branch July 18, 2025 11:00
mydea added a commit that referenced this pull request Jul 25, 2025
This adds a lint rule to avoid usage of `Object.assign` (we already have
similar rules for other things that are not polyfilled). We can just use
object spread instead, which _is_ polyfilled.

Fixes #16970

Replacing #17053 as
that stalled on CI somehow...
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.

3 participants