Skip to content

Inconsistencies with node core #6

Open

Description

@feross

Activity

  1. Gozala commented on Feb 27, 2015

    @Gozala
    Owner

    @medikoo is maintaining this repo, so I don't want to make API changes without him being ok with that. I think work that @feross is doing is very important & it would be a shame if do not support him, regardless of our API preferences.

  2. feross commented on Feb 27, 2015

    @feross
    Author

    Thanks @Gozala :)

    The goal of this module is to match the node/iojs querystring module, right? Seems like API changes shouldn't be debated in this repo, but in the node/iojs projects before API changes are made. Once node/iojs commit to an API, the module ought to just mirror it :) At least, that's what I do in buffer.

  3. medikoo commented on Mar 1, 2015

    @medikoo
    Collaborator

    @Gozala this can't be reliable achieved without getting back to single module version. I'm fine with this, as in my work I rely more on querystring2 package.

    If you're also ok with it, in some free moment I can make it so it's single module with latest node.js implementation.

  4. philipwalton commented on Apr 2, 2015

    @philipwalton

    I just encountered this issue and completely agree with @feross.

    If you're not going to match the API exactly, at a bare minimum the differences should be documented. As it is today I had to read through the code to see if my implementation was buggy or if this library just didn't support this option.

  5. Gozala commented on Apr 2, 2015

    @Gozala
    Owner

    @medikoo sure let's merge with your querystring2 if resolves this issue for everyone.

  6. emilbayes commented on Sep 26, 2015

    @emilbayes

    Any progress on this? Browserify seems to rely on the module by default, so it's a shame that it's not 1:1 with Node core My bad, the browserify README.md links to this module, but the package.json specifies querystring-es3

  7. added a commit that references this issue on Jan 2, 2017
  8. medikoo commented on Apr 11, 2017

    @medikoo
    Collaborator

    Should be addressed with #20 it covers also ES3 version, PR's are very welcome (and I will handle them promptly).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions