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

Can the idleTime be set after initialisation? #44

Open
osawyer opened this issue May 24, 2020 · 3 comments
Open

Can the idleTime be set after initialisation? #44

osawyer opened this issue May 24, 2020 · 3 comments

Comments

@osawyer
Copy link

osawyer commented May 24, 2020

It would be great to be able to change the ideTime option that you can set initially in the options. In my case, I have users that want to be able to configure the idle time-out of modals. For this, the timeout setting is stored in localStorage, and I've got it fetching from there to set on the idleTime option, but I can't see a way of setting it after the initial app load. Only solution I could think of so far is to force a refresh, but I'm reluctant to do that as I believe it's bad practice in SPAs. Appreciate the help!

@osawyer
Copy link
Author

osawyer commented May 24, 2020

Actually looks like three potential PRs for resolving this already exist! It's clear this is seen as an essential feature, and people are contributing! It would be great to get something merged in. :)
#43 #37 #41

@snake-py
Copy link

snake-py commented Jan 5, 2022

Seems like it is not going to be merged somewhere soon, it would be great if anyone has a solution for this and would be willing to share how they did it.

@gabrielstuff
Copy link
Member

HI there 👋 ! I wish you all the best for 2022. Thanks for keeping the project alive.
I know it has been a long time and I should have take the time to merge these pull request earlier.

I wanted to first clean idle-js dependency and then start working on idle-vue.
The work on idle-jshas started and I plan to release the patch tomorrow.

For Idle-vue, there are actually many issues because:

  • vue3 has been released
  • dependencies are not up to date
  • dev stack is not up to date
  • bugs have to fixed :)

Ok, back to code, hopping to give you more info tomorrow

Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants