Truncate rio fields per rio max length #316
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdemare
force-pushed
the
truncate-rio-fields
branch
from
89a50a9 to
524cfdf
Compare
mdemare
force-pushed
the
truncate-rio-fields
branch
from
524cfdf to
46275b8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implemented due to comment by Herman van Dompselaar:
ik lees toevallig even mee. Je zou nog kunnen overwegen om de inhoud na 1000 karakters af te kappen voor rio. Want het is wel geldige ooapi. Als het dan niet allemaal in rio komt is blijkbaar geen probleem. Of dan moeten ze het veld inkorten. Maar zo hebben instellingen wel de mogelijkheid meer karakters te gebruiken in ooapi die voor andere toepassingen wel relevant zijn.