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

Feature request : add a login(account) option to sync all settings using account #506

Closed
kanatkubash opened this issue Mar 5, 2018 · 24 comments

Comments

@kanatkubash
Copy link

kanatkubash commented Mar 5, 2018

Issuehunt badges

It would very great if you have added something like account or log in, so that you can log in to vs code and have all settings synced across all logged in vs code instances - so you don't have to remember gist id

By @shanalikhan , here is the initial page UI.


  1. A page will be opened inside code [like Git Lens extension] initially when the user does not have anything configured.
  2. Page contains Settings Sync information and some good UI
  3. A Button should be present with a current option as "Github"
  4. When user click button, Username and password and Gist ID fields should be shown to the user to fill them.
  5. On entering details user should click on submit button.
  6. On click event should get those values and just close that tab.

Join our slack channel for discussion directly with me while you develop so i can assist you.


IssueHunt Summary

arnohovhannisyan arnohovhannisyan has been rewarded.

Backers (Total: $318.00)

Submitted pull Requests


Tips


IssueHunt has been backed by the following sponsors. Become a sponsor

@shanalikhan
Copy link
Owner

Low priority.
PR is welcome for it.

@IssueHuntBot
Copy link

@BoostIO funded this issue with $60. Visit this issue on Issuehunt

@IssueHuntBot
Copy link

@loadbalance-sudachi-kun funded this issue with $256. Visit this issue on Issuehunt

@shanalikhan
Copy link
Owner

This issue is available in bounty program, fix and earn the money 😄

@IssueHuntBot
Copy link

@zhangzhishan has started working. Visit this issue on Issuehunt

@shanalikhan
Copy link
Owner

@zhangzhishan is there any progress? I can assist you if you have started working on it.
You can send a PR, and we can discuss over there.

@shanalikhan shanalikhan added this to the Backlog milestone Oct 11, 2018
@zhangzhishan
Copy link

@zhangzhishan is there any progress? I can assist you if you have started working on it.

I have a design and working on the account back-end work.

@shanalikhan
Copy link
Owner

Its been a month and its the paid one.
It would be great, if you can send a PR for (work in progress) so i can see the changes while you are making progress.

@shanalikhan
Copy link
Owner

This issue is opened again for Bounty.

Amount funded
$316

@PicchiKevin
Copy link

What about connecting with a github account ?
Is this what you mean ?

@IssueHuntBot
Copy link

@aashutoshrathi has funded $2.00 to this issue.


@shanalikhan
Copy link
Owner

@PicchiKevin

It means, you currently Settings Sync require github account, therefore github Button to connect is required in order to enter the required details

@aashutoshrathi
Copy link

@shanalikhan You mean instead of asking access token we have to implement Auth using GUI right?

@shanalikhan
Copy link
Owner

Yes.
Auth using GUI alongwith GUI that should have all the things present for the Settings Sync.
Example is the page for Git Lens that shows up when you install that extension.

@janat08
Copy link

janat08 commented Mar 26, 2019

For this to be secure it will need backend. Are you okay with this, as hypothetically one day it will crash or something, or be overloaded and you're on the hook (ill use zeit)?

@kanatkubash
Copy link
Author

@janat08 Maybe open up a browser page for github oauth consent screen, where callback is set to local server spawned within extension, and on access grant, it just picks up access token and stores it ?

@janat08
Copy link

janat08 commented Mar 26, 2019

I suppose that makes sense.

@janat08
Copy link

janat08 commented Mar 26, 2019

Well I was reffering to secret code of oauth application, which I assume would have to be shared in the extensions if done without the backend?

@kanatkubash
Copy link
Author

@janat08 Yeah, I missed this point. But I believe there are no rogue extensions , that will try to use the token. Also tokens scope is limited to gists. @shanalikhan What do you think ?

@qti3e
Copy link

qti3e commented Jun 30, 2019

Also, it's possible to use Firebase... I would be happy to work on this issue :) but I don't know the current state.

@janat08
Copy link

janat08 commented Jun 30, 2019

Its like totally done, they decided to do some extra prep work before merge.

shanalikhan pushed a commit that referenced this issue Jul 1, 2019
* Updated to task api 2.0.0 and fixed tests

* Set "extensionKind": "ui" to support remote development #61

Fixes #870. See that issue for details

* Clean up previous commits into one

* #800 #515 #854

* Utilized pragmaUtil Functions for kb.json file

* Typo fix

* Added universalKeybindings setting

* chore(package): update @types/node to version 12.0.0 (#873)

* Cleaned up toggling commented settings (#877)

* Cleaned up toggling commented settings

* Updated to include fix by @ioprotium

* Fix warning with webpack

* Update UI

* Change height to max-height

* Add image locally and move it to the top

* Added documentation for tests in CONTRIBUTING.md (#881)

* fix(package): update fs-extra to version 8.0.0 (#882)

* chore(package): update @types/fs-extra to version 7.0.0 (#885)

* chore(package): update @types/node to version 12.0.1 (#883)

* fix(package): update fs-extra to version 8.0.1 (#884)

* Update UI to fit guidelines

* chore(package): update @types/node to version 12.0.2 (#887)

* Improve UI and functionality

* Match BG of theme and properly contrast text

* Fix issues with themes

* Fix image not showing up with light theme

* Fix issues with contrast

* Fix issue with VS Code's WebView

* Update UI and functionality

* Fix potential issue with light themes

* Fix issues with theme on modal

* Refactor

* Add new (but experimental) localizations (#898)

* chore(package): update clean-webpack-plugin to version 3.0.0 (#899)

*  #891

* Update settings page after a reset

* Improve code

* fix(clean-webpack-plugin): (#901)

clean-webpack-plugin was recently updated, and it had breaking changes.

* chore(package): update @types/node to version 12.0.3 (#897)

* #668

* fix(OSS):

enums.ts
----
Allow for setting os type with less code

environmentPath.ts
----
Find code folder and extensions folder more efficiently
Get OS type more efficiently

settings.ts
----
Ignore all state files

sync.ts
----
Adapt for changes in pluginService

pluginService.ts
----
Use vscode command to install extensions
Clean up code and simplify names

* Install extensions in order

* Comment legacy code instead of deleting it

* Fix extension install

* Fix issue with extensions always being deleted

* Get code path more efficiently

* Make sure to escape spaces in cli path

* Fix issues with portable builds

* Support Windows and certain editions

* Improve method for finding extension folder

* Start using API for installation

* Prepare for new API command

* Get ready for new API command

* Fix issue with installation

* Commit requested changes

* #668

* Format pluginService.ts (#906)

* #668

* Throw error

* Try to fix issues with getting missing

* chore(package): update @types/node to version 12.0.7 (#904)

* chore(package): update @types/node to version 12.0.8 (#908)

* #668

* #668

* #668

* #839

* Support multiple instances

* Completely switch to state

* Update to work properly

* Move setting classes to their own models

* Update service names

* Only auto upload using focused window

* Resolve merge conflicts

* #886

* Resolve locale properly

* Clean constructor

* Use state instead of passing in argument

* Update to be compatible with v3.3.0 changes

* Fix readme

* Fix package.json

* Add new settings

* Increase contrast

* Update

package.nls.*.json
----
Add localizations for setting names and placeholders.

github.oauth.service.ts
----
Handle errors in a more user-facing way
Support GitHub enterprise
Show message to user after success

webview.service.ts
----
Use new localizations for names and placeholders

* Bug fix and upload images

* Add support for commits to master (release notes)

* Fix issue

* Fix another issue with release notes

* Update release note template

* Update release notes

* Don't open gist selection if there aren't any gists

* Allow user to view gist

* Revert accidental change

* Support public gist

* Add css, js, and fonts to repo

* Improve font injection

* Revert accidental change
shanalikhan pushed a commit that referenced this issue Jul 1, 2019
* Fix webpack build process

* Only ignore warning from express
shanalikhan pushed a commit that referenced this issue Jul 2, 2019
shanalikhan pushed a commit that referenced this issue Jul 2, 2019
* Add button to download public gist

* Download after getting public gist
shanalikhan pushed a commit that referenced this issue Jul 5, 2019
@shanalikhan
Copy link
Owner

v3.4.0 is released containing this feature by @arnohovhannisyan
Update this extension. Let us know what you think and where we can improve the UI.

@shanalikhan shanalikhan unpinned this issue Jul 15, 2019
@issuehunt-oss
Copy link

issuehunt-oss bot commented Jul 18, 2019

@shanalikhan has rewarded $222.60 to @arnohovhannisyan. See it on IssueHunt

  • 💰 Total deposit: $318.00
  • 🎉 Repository reward(20%): $63.60
  • 🔧 Service fee(10%): $31.80

@issuehunt-oss issuehunt-oss bot added the 🎁 Rewarded on Issuehunt This issue has been rewarded on Issuehunt label Jul 18, 2019
@shanalikhan
Copy link
Owner

As it was released on v3.4.0
Closing this ticket.

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

8 participants