modelTypeExpression fix #1918
Open
modelTypeExpression fix #1918
Conversation
This file contains 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
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.
Hi @IvanIlyichev . I am tasked with this issue. After days of debugging I found that the 'modelType' when entityType is on 'js-mode' is always undefined resulting in no results on Display Property this is also the case for queryBuilder. My assumption for this bug is that the entityType for 'js-mode' is being saved as an object {_code:'......',} which make sense since the value must be dynamic. Given my pushed code can you please guide on how I can best achieve the task requirements. Here is the quick link to reproduce the bug.