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
This would really help when we're working with models coming from the server. I have to either add the label and group properties to my back-end model solely for the autocomplete (which the server shouldn't really know about) or I have to do the same on the front-end or extend the TS class with the AutocompleteClient - which forces me to use a different model than my usual.
I know in JavaScript you can use a object["propertyName"] syntax to get properties so enabling us to configure their name shouldn't be too difficult.
It would really help improve code maintainability.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This would really help when we're working with models coming from the server. I have to either add the label and group properties to my back-end model solely for the autocomplete (which the server shouldn't really know about) or I have to do the same on the front-end or extend the TS class with the
AutocompleteClient
- which forces me to use a different model than my usual.I know in JavaScript you can use a
object["propertyName"]
syntax to get properties so enabling us to configure their name shouldn't be too difficult.It would really help improve code maintainability.
The text was updated successfully, but these errors were encountered: