Fix: PyMISP must jsonify MISPTag's local field as an int #1171
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
In MISP, MISPTag's local field is jsonify as an int, however PyMISP jsonify it as a string. This is unexpected.
dragsu
force-pushed
the
fix-local-key-as-int
branch
from
ee5e7d6
to
512019b
Compare
|
This is a bug in MISP #1124 (comment) and this fix is not relevant. |
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.
In MISP, MISPTag's local field is jsonify as an int, however, PyMISP jsonify it as a string. This is unexpected.