Skip to content
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.

fix(media-marshaller): do not propagate undefined value #1245

Merged
merged 1 commit into from
May 9, 2020

Conversation

CaerusKaru
Copy link
Member

In certain cases, users may need to dynamically set the value of
an input to undefined. This value should then be ignored in
place of another value in the fallback mechanism.

Fixes #1207

In certain cases, users may need to dynamically set the value of
an input to `undefined`. This value should then be ignored in
place of another value in the fallback mechanism.

Fixes #1207
@CaerusKaru CaerusKaru added this to the 9.0.0-beta.30 milestone May 9, 2020
@CaerusKaru CaerusKaru merged commit b05d51a into master May 9, 2020
@CaerusKaru CaerusKaru deleted the adam/fix-issue-1207 branch May 9, 2020 22:10
@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 Jun 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setting ngClass breakpoints to undefined is not working as expected
2 participants