-
Notifications
You must be signed in to change notification settings - Fork 7
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
Expose dps.report user token or list where to find it #24
Comments
Im currently working on this here: https://github.com/punsii2/arcdps-uploader/tree/user-token The change will currently:
One thing that i did not do yet do but which could probably be done is to add the userToken to the log-entries for each successful upload. But i think having one persistent token that is visible in the settings should be enough. If you relay want this as fast as possible you can use the release from my fork |
Store the dps.report userToken response and persist it in the config. Send the stored userToken with every upload. Add the userToken to the configuratoin UI. This allows setting, resetting and disabling the userToken. At the moment only one userToken can be stored but the current implementation could be extended easily to support multiple tokens and the ability to switch between them.
Store the dps.report userToken response and persist it in the config. Send the stored userToken with every upload. Add the userToken to the configuratoin UI. This allows setting, resetting and disabling the userToken. At the moment only one userToken can be stored but the current implementation could be extended easily to support multiple tokens and the ability to switch between them.
Store the dps.report userToken response and persist it in the config. Send the stored userToken with every upload. Add the userToken to the configuratoin UI. This allows setting, resetting and disabling the userToken. At the moment only one userToken can be stored but the current implementation could be extended easily to support multiple tokens and the ability to switch between them.
Store the dps.report userToken response and persist it in the config. Send the stored userToken with every upload. Add the userToken to the configuratoin UI. This allows setting, resetting and disabling the userToken. At the moment only one userToken can be stored but the current implementation could be extended easily to support multiple tokens and the ability to switch between them.
Please add a way to find the user token used by uploader,
this would be one way to easily integrate with other tools such as Aleeva, mentioned in #11
The text was updated successfully, but these errors were encountered: