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

Conversation

CaerusKaru
Copy link
Member

When the element itself is initialized within an NgForOf element,
previously the Flex direction initialization would take place too
early. As a result, the directive would not update on parent
changes correctly. This commit corrects this by adding the
initialization logic into OnInit.

Fixes #1160

When the element itself is initialized within an NgForOf element,
previously the Flex direction initialization would take place too
early. As a result, the directive would not update on parent
changes correctly. This commit corrects this by adding the
initialization logic into OnInit.

Fixes #1160
@CaerusKaru CaerusKaru added this to the 9.0.0-beta.30 milestone May 7, 2020
@CaerusKaru CaerusKaru merged commit 93a426a into master May 7, 2020
@CaerusKaru CaerusKaru deleted the adam/fix-issue-1160 branch May 7, 2020 23:45
@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 7, 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.

fxFlex not switching max-width and max-height
2 participants