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
RTT will avoid processing a Ricardian contract if the length of the raw summary is greater than 116 characters.
Furthermore, if the generated summary is greater than 116 characters, RTT will simply truncate the generated summary string to fit. I consider this truncation to be a bug: if the spec required the generated string to be no more than 116 character (which I'm not sure if it does because it is ambiguously worded) then it should not return any successful result. But I think it would be better for the library to just return the full generated string, however long it is, and allow the authenticate UI to enforce any truncation it wants.
Better yet, if this (EOSIO/ricardian-spec#20) proposed change to the Ricardian spec is adopted, then RTT should not enforce any limit on the summary. Such a limit could optionally be enforced in the authenticator UI.
The text was updated successfully, but these errors were encountered:
RTT will avoid processing a Ricardian contract if the length of the raw summary is greater than 116 characters.
Furthermore, if the generated summary is greater than 116 characters, RTT will simply truncate the generated summary string to fit. I consider this truncation to be a bug: if the spec required the generated string to be no more than 116 character (which I'm not sure if it does because it is ambiguously worded) then it should not return any successful result. But I think it would be better for the library to just return the full generated string, however long it is, and allow the authenticate UI to enforce any truncation it wants.
Better yet, if this (EOSIO/ricardian-spec#20) proposed change to the Ricardian spec is adopted, then RTT should not enforce any limit on the summary. Such a limit could optionally be enforced in the authenticator UI.
The text was updated successfully, but these errors were encountered: