Use max_topic_length instead of hardcoded limit of 60 #1413
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #307
Changes
maxTopicLengthfield to the initial snapshot to retrieve the value from the server.maxTopicLengthinPerAccountStorefrom the initial snapshot.ComposeTopicControllerincompose_boxto use the value fromPerAccountStore.route/messages.dartapp_en.arbto dynamically display the maxTopicLength value in the topic length error message, replacing the hardcoded "60"_sendmethod ofcompose_boxto use the modified error message that contains the dynamicmaxTopicLengthTesting
PerAccountStoreinstead of the hardcoded value.maxTopicLengthvariants.