This repository has been archived by the owner on Oct 4, 2019. It is now read-only.
Not write follow operations dump in wrong cases #1333 #1334
+9
−1
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
soft-bagel-93
force-pushed
the
1333-operation-dump-fix-custom-json
branch
from
2a6002a to
bf2c337
Compare
soft-bagel-93
force-pushed
the
1333-operation-dump-fix-custom-json
branch
from
bf2c337 to
808599b
Compare
afalaleev
approved these changes
Jun 18, 2019
zxcat
approved these changes
Jun 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #1333 for operation dump (#1333 is actual only for it).
followerorfollowingaccount is not exists. (Note: accounts cannot be removed, therefore they can be checked for presence after LIB)