Skip to content
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

More flexibility for sessionContext handling #31

Closed
OGKevin opened this issue Oct 12, 2017 · 0 comments
Closed

More flexibility for sessionContext handling #31

OGKevin opened this issue Oct 12, 2017 · 0 comments
Assignees
Milestone

Comments

@OGKevin
Copy link
Contributor

OGKevin commented Oct 12, 2017

Steps to reproduce:

  1. Try and find out if your session context is expired

What should happen:

  1. There is a way to know if your session has expired without resetting/calling ensureSesiosActive()

What happens:

  1. There is no way to achieve such thing

Extra info:

Why

  • This way you wont have to execute this code before each call but only if your session did expire
api_context.ensure_session_active()
api_context.save(filename_bunq_config_full)

Which means you will be saving an unchanged context on each call

@OGKevin OGKevin self-assigned this Oct 12, 2017
OGKevin added a commit that referenced this issue Oct 12, 2017
dnl-blkv added a commit that referenced this issue Oct 24, 2017
Added isSessionExpired() method #31.
@OGKevin OGKevin added this to the 0.12.1 milestone Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant