TRD: Better Handling of Value Syncing #615
StephenRiosDev
started this conversation in
Technical Research Documents
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Came about from PR: https://github.com/AlaskaAirlines/auro-formkit/pull/1233/files
As you can see from this PR, we were running into an issue where we weren't waiting for the values to be sync'd between the internal
auro-inputand the parent component inauro-comboboxandauro-datepicker.This is a common paradigm in our components where we implement our own components internally and share reactive property names between them that need to stay in sync, and certain operations to be performed when this syncing occurs.
This discussion is to establish a pattern that all developers agree to follow when implementing this paradigm, or updating a component to follow this paradigm.
Beta Was this translation helpful? Give feedback.
All reactions