Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 07 12:56
    dependabot[bot] labeled #28
  • May 07 12:56
    dependabot[bot] opened #28
  • May 07 12:56

    dependabot[bot] on npm_and_yarn

    Bump url-parse from 1.4.4 to 1.… (compare)

  • Apr 13 00:40
    berg2043 commented #26
  • Mar 15 11:06
    lonix1 edited #27
  • Mar 15 08:54
    IJustDev commented #27
  • Mar 13 12:44
    lonix1 commented #27
  • Mar 13 12:44
    lonix1 commented #27
  • Mar 13 11:50
    IJustDev commented #26
  • Mar 13 10:50
    IJustDev commented #27
  • Mar 13 07:56
    lonix1 opened #27
  • Mar 13 07:52
    lonix1 opened #26
  • Mar 12 20:17

    IJustDev on 2.0.0

    (compare)

  • Mar 12 20:17

    IJustDev on 2.0.0

    (compare)

  • Mar 12 20:17

    IJustDev on master

    refactor: bump version (compare)

  • Mar 12 20:14
    IJustDev closed #24
  • Mar 12 20:14

    IJustDev on master

    feat: add test environment with… fix: #24 remove baseurl field (compare)

  • Mar 12 20:14

    IJustDev on 2.0.0

    feat: add test environment with… fix: #24 remove baseurl field (compare)

  • Mar 12 19:47
    IJustDev commented #24
  • Mar 12 19:46
    IJustDev closed #25
LJ
@ljoonal

@IJustDev I'm thinking of making radical changes that would pretty much re-write everything, and thought I'd ask you if you'd prefer that to be merged to your repo or if I should make a completely new project? :)

Since I don't think that it's the best of ideas to make copies of basically the same thing, but then neither is taking over someone else's project a good idea :D

IJustDev
@IJustDev
First of all: Thank you very much for your question.
I agree. Since I don't like the name of the project itself I would agree on your idea of creating a new project. We could then archive this project and place a link in the README.md to the new one. But this will lead to problems. Currently I published the pkg to the vscode store. But we want the users to install the new one. Do you have any idea on how to accomplish that?
LJ
@ljoonal
Dunno about that, I haven't looked at Microsoft's vscode-store publishing details yet. One option that I can quickly think off (that would work but be annoying to users) is to make a new final version which contains code to (probably only once after updating the addon) to show a popup telling the user to change to the new addon as the old one is being deprecated... But anyways that's still in the future, as I don't know how long it'll take me to get a version ready that I'm comfortable with publishing :D
IJustDev
@IJustDev
Okay start then I would be grateful to help you. Once created please link the new repository in this chat please. You can also create a pull request for a link in the README.md