-
Notifications
You must be signed in to change notification settings - Fork 96
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
Remove sign in and sign out features - Closes #4317, #4463 #4324
Remove sign in and sign out features - Closes #4317, #4463 #4324
Conversation
@isalga please don't merge the pr when is done |
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.
Good job @isalga!
This pull request can not be merged unless the change API objective is completed to support the way login to account to be able to create transaction or access endpoints. All of the SDK v5 features are closely integrated, so we intend to keep this PR until v6 API integration is completed. |
The base branch was changed.
c886ea1
to
565954e
Compare
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.
I think most of the e2e tests whose pages are on private routes(i.e depended on login) might fail.
Because most these tests uses the /^I login as ([^\s]+) on ([^\s]+)$/
test scenario to login as either of the network types (i.e mainnet
, testnet
or devnet
)
@@ -20,10 +19,10 @@ describe('Reducer: settings(state, action)', () => { | |||
it('should return updated settings if action.type = actionTypes.settingsUpdated', () => { | |||
const action = { | |||
type: actionTypes.settingsUpdated, | |||
data: { autoLog: false }, | |||
data: { testSetting: false }, |
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.
the naming convention here seems confusing possibly the term useTestSetting
would be okay I think
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.
@eniolam1000752 we dont need this settings anymore could you please remove it
d9e49a2
to
d3874c8
Compare
8bc1c04
to
e87acfc
Compare
4d530f0
to
122cb47
Compare
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.
LGTM
What was the problem?
This PR resolves #4317
How was it solved?
How was it tested?