updated lookup component to handle changes from a non-null value to a…#208
Open
mrichmon12 wants to merge 1 commit intoappiphony:masterfrom
mrichmon12:handleLookupNonNullValueChange
Open
updated lookup component to handle changes from a non-null value to a…#208mrichmon12 wants to merge 1 commit intoappiphony:masterfrom mrichmon12:handleLookupNonNullValueChange
mrichmon12 wants to merge 1 commit intoappiphony:masterfrom
mrichmon12:handleLookupNonNullValueChange
Conversation
…nother non-null value
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Noticed a bug where if you were changing the value of the lookup component from one non-null value to another in a controller/helper it would not fetch the label and sub-label for the updated key. Added check to see if the value is changing to the existing event handler.