Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 12 22:31
    DavidGoodenough closed #22
  • Mar 26 14:09
    peacememories opened #41
  • Mar 26 14:06
    peacememories opened #40
  • Mar 21 19:42
    IJustDev commented #36
  • Mar 21 15:11
    meichthys commented #36
  • Mar 21 15:04
    meichthys commented #36
  • Mar 08 21:30
  • Feb 26 10:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • Feb 26 10:22
    dependabot[bot] closed #38
  • Feb 26 10:22
    dependabot[bot] commented #38
  • Feb 26 10:22
    dependabot[bot] labeled #39
  • Feb 26 10:22

    dependabot[bot] on npm_and_yarn

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

  • Feb 26 10:22
    dependabot[bot] opened #39
  • Feb 17 21:50

    dependabot[bot] on npm_and_yarn

    (compare)

  • Feb 17 21:50
    dependabot[bot] closed #34
  • Feb 17 21:50
    dependabot[bot] commented #34
  • Feb 17 21:50
    dependabot[bot] labeled #38
  • Feb 17 21:50
    dependabot[bot] opened #38
  • Feb 17 21:50

    dependabot[bot] on npm_and_yarn

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

  • Feb 11 19:28
    dependabot[bot] labeled #37
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
MeIchthys
@meichthys
@ljoonal Have you started work on this yet?