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
Describe the bug
Some fields can contain complex text data, we want to make data that is complex read only on the client. This is not a field by field setting, but for each string of data from a project. In FwDataMiniLcm we have the method FromLcmMultiString which converts from Lcm to MiniLcm, we want to augment it like this to detect if the data should be readonly:
privateMultiStringFromLcmMultiString(ITsMultiStringmultiString){varresult=newMultiString(multiString.StringCount);for(vari=0;i<multiString.StringCount;i++){vartsString=multiString.GetStringFromIndex(i,outvarws);if(tsString.RunCount==1){result.Values.Add(GetWritingSystemId(ws),tsString.Text);}else{//todo, mark this value as read only so we don't edit it and overwrite text}}returnresult;}
note checking that RunCount is 1. I'm not sure how we want to mark a value as read only. One option would be to add another ws key "{wsId}-ro": "true", or we could modify the text itself, but that would be more complicated as it would require escaping. The frontend could then respect this configuration and make those text fields readonly. Later on once we model and support runs we can change this and the frontend won't be readonly anymore.
The text was updated successfully, but these errors were encountered:
Describe the bug
Some fields can contain complex text data, we want to make data that is complex read only on the client. This is not a field by field setting, but for each string of data from a project. In FwDataMiniLcm we have the method
FromLcmMultiString
which converts from Lcm to MiniLcm, we want to augment it like this to detect if the data should be readonly:note checking that RunCount is 1. I'm not sure how we want to mark a value as read only. One option would be to add another ws key
"{wsId}-ro": "true"
, or we could modify the text itself, but that would be more complicated as it would require escaping. The frontend could then respect this configuration and make those text fields readonly. Later on once we model and support runs we can change this and the frontend won't be readonly anymore.The text was updated successfully, but these errors were encountered: