This repository has been archived by the owner on Sep 21, 2022. It is now read-only.
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.
This is required in order to be consistent with:
api-utils/lib/encodeOpaqueId.js
Line 20 in f769070
Since the entire encoding/decoding of IDs was built for a reason that is no longer valid, we've found it very practical to simply set the environment variable REACTION_SHOULD_ENCODE_IDS to false. This makes development considerably easier, especially for quick API tests with graphQL playground.
But in order for that to work,
decodeOpaqueId()
should also check for the env variable. If we don't do that,decodeOpaqueId()
can return wrongnamespace
andid
values.(Note that
decodeOpaqueId()
did NOT always fail prior to our change. For example, decodingreaction/mediaRecord:xifjgK9ckbptZ2ew2
will yield a null namespace and return the ID as is (because there's no:
character to split on I believe), whereas decoding IDreaction/mediaRecord:dTp6az9ghgoLSGGTo
will yield a namespace equal tou
and a wrong ID)