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

Expose dps.report user token or list where to find it #24

Closed
PathosV opened this issue Feb 18, 2022 · 2 comments
Closed

Expose dps.report user token or list where to find it #24

PathosV opened this issue Feb 18, 2022 · 2 comments

Comments

@PathosV
Copy link

PathosV commented Feb 18, 2022

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

@punsii2
Copy link
Contributor

punsii2 commented Jun 3, 2022

Im currently working on this here: https://github.com/punsii2/arcdps-uploader/tree/user-token
I will try push this and other changes into the main Repo over the next days.

The change will currently:

  • automatically store the userToken and reuse it for every upload
  • display the userToken
  • allow you to set a custom userToken
  • allow you to disable the userToken (such that a new one will be created for every upload again)

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
It already works for me but some more testing/feedback would be appreciated.

punsii2 added a commit to punsii2/arcdps-uploader that referenced this issue Jun 16, 2022
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.
punsii2 added a commit to punsii2/arcdps-uploader that referenced this issue Jun 16, 2022
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.
punsii2 added a commit to punsii2/arcdps-uploader that referenced this issue Jun 16, 2022
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.
punsii2 added a commit to punsii2/arcdps-uploader that referenced this issue Jun 16, 2022
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.
nbarrios added a commit that referenced this issue Oct 17, 2022
@nbarrios
Copy link
Owner

nbarrios commented Nov 1, 2022

Thanks @punsii2 for the pr. This is now merged and working in the v0.9.7.

@nbarrios nbarrios closed this as completed Nov 1, 2022
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