Near section about text-by and value-by (which are easy thing to understand) add small text about track-by. Likely, user want to use track-by within text-by (but he can ignore track-by if value-by is used). I must be alert with type info.
In case if you're using text-by without value-by, don't forget to add track-by. Otherwise Select may not hightlight correct options if they selected.
If you know how to say it better, you can change the text. The problem here because objects used in value and options can be completely different and to have a way to compare them, we use text-by. For me, selected options were highlighted because objects are the same on frontend. After page reloaded, saved data loaded from backend objects with the same structure are different objects, therefore select wasn't able to compare them because track-by wasn't provided. I'd like users not to fall in this trap.
Near section about text-by and value-by (which are easy thing to understand) add small text about track-by. Likely, user want to use track-by within text-by (but he can ignore track-by if value-by is used). I must be alert with type
info.If you know how to say it better, you can change the text. The problem here because objects used in value and options can be completely different and to have a way to compare them, we use
text-by. For me, selected options were highlighted because objects are the same on frontend. After page reloaded, saved data loaded from backend objects with the same structure are different objects, therefore select wasn't able to compare them becausetrack-bywasn't provided. I'd like users not to fall in this trap.