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.

Sign up for GitHub

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

Jump to bottom

yarn dev : better handling of expired token or token associated to another cozy #333

Open
doubleface opened this issue Aug 27, 2018 · 2 comments
Open

yarn dev : better handling of expired token or token associated to another cozy #333

doubleface opened this issue Aug 27, 2018 · 2 comments
Labels
high

Comments

@doubleface
Copy link
Collaborator

In this case we should remove the token and try to recreate it.
@ptbrowne
Copy link
Contributor

IMHO, all the necessary info to connect to a particular cozy should be kept in a single file.

Here we have pieces of informations in 3 places :

  • .token.json
  • .account
  • konnector-dev-config.json

Merging them into a single file would lead to simpler dev experience IMHO.

@doubleface
Copy link
Collaborator Author

Right, except the .account file is not needed anymore since e1608d5

But yes, the token could be memorized in konnector-dev-config.json for example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@doubleface @ptbrowne