You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be great to automatically set the public properties of the screen when query data is returned. This would reduce the number of assignments and make the code more pleasant for multiple declarations.
As an example, now you need to specify properties yourself:
This discussion was converted from issue #1640 on April 14, 2021 09:39.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is your feature request related to a problem? Please describe.
It would be great to automatically set the public properties of the screen when query data is returned. This would reduce the number of assignments and make the code more pleasant for multiple declarations.
As an example, now you need to specify properties yourself:
Describe the solution you'd like
If we assigned all public properties to autocomplete from the query result, then:
That is, We have automatically assigned to the
user
property the data obtained with the same key.Additional context
This is a breaking change, as the existing codebase can specify public properties with the same names as keys. Only suitable for the major version.
Beta Was this translation helpful? Give feedback.
All reactions