-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redesigned the framework to make it less vulnerable to native exceptions. #951
Closed
Closed
Changes from 1 commit
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
300e0fa
improve the code with the help of new try-catch
radetsky 8d2eb52
integrate isBase64 into code
radetsky a47fad8
review Obj-C code to make all try-catch and error checks
radetsky 9a27632
fix an errors
radetsky 241e0ac
review Java code
radetsky 9907cb5
review Obj-C code
radetsky ecb3457
review Javascript code
radetsky 0d9de20
moved old example and add ThemisTest for RN app
radetsky 9c8377f
new Android Studio support file
radetsky 90a0401
failed/passed fixes in order
radetsky c4eecd6
comparator can return nil without an error
radetsky 6ecbec4
update example app
radetsky 19496ce
Merge branch 'release/0.14' into rad-dev
radetsky e3a0322
changelog update
radetsky 84218b2
check int value before casting to unsigned char
radetsky cdd443f
fix the compare procedure; var naming due the suggestion;
radetsky 480702a
remove privateKey from secureMessageVerify functions
radetsky 99342d1
remove publicKey from secureMessageSign64
radetsky 297c93d
rewrite Obj-C code to use NSError instead of try/catch
radetsky cc5c3bb
fix the tests. The issue was in incorrect display of error
radetsky aa72af2
updated the code according to the comments
radetsky 35ec1e9
updated the code according to the comments
radetsky 913fec3
move examples to the previous state
radetsky File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it break backward compatibility? do we know that these methods are used anywhere or by someone?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A little. Verify method now has only two required parameters. I deleted the middle one - an optional private key. The sign method is compatible.
I think we should describe the changes in our documentation for react-native-themis.
The GitHub search tool returns only 8 code results and all results contain in our repositories.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No such thing. Either applications are going to break after update, or they will not.
Aren't these methods semi-private? As in, they are an implementation detail of ReactNative Themis, and the users will not be calling them directly, but rather through JS code?
Though, I see JS API being changed as well, so it's a genuine breaking change.
Please, don't make breaking changes in patch releases, that's irresponsible.
In fact, better avoid making breaking changes at all until the next major version. Deprecations are okay though.
Or else, be honest, slap a prominent red banner in ReactNative documentation that the package is currently under development, is unstable, anything can be changed at any time, and it will be totally the user's fault if their application stops working after an update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. I returned the middle param privateKey in the public API function. But mark it as unused and optional.