8000 assert: apply minor refactoring by Trott · Pull Request #11511 · nodejs/node · GitHub
  • [go: up one dir, main page]

    Skip to content

    Conversation

    @Trott
    Copy link
    Member
    @Trott Trott commented Feb 22, 2017
    • Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    • Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    • Favor === over == in two places.
    Checklist
    • make -j4 test (UNIX), or vcbuild test (Windows) passes
    • commit message follows commit guidelines
    Affected core subsystem(s)

    assert

    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    @Trott Trott added the assert Issues and PRs related to the assert subsystem. label Feb 22, 2017
    @Trott
    Copy link
    Member Author
    Trott commented Feb 22, 2017

    }

    if (Object.prototype.toString.call(expected) == '[object RegExp]') {
    if (Object.prototype.toString.call(expected) === '[object RegExp]') {
    Copy link
    Member

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Could we import objectToString from internal/util at the top and just call it here? And if so, would that be more readable?

    Copy link
    Member Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    I could go either way on it. (Let me know if you feel strongly one way or the other.)

    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Importing it is probably better. If we ever move toward storing Object.prototype.toString in a variable to prevent tampering in userland code, it would require less updating.

    Copy link
    Member Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Turns out there's already a function internal to assert.js for this.
    ¯\(ツ)

    Copy link
    Member Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    (And I see that function is replaced with the one from internal/util in #11128.)

    Copy link
    Member
    @joyeecheung joyeecheung left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    +1 to use require('internal/util').objectToString in case there is another PR to prevent Object.prototype.toString.call() from being tampered with, though it doesn't need to happen in this PR..#11128 do use objectToString though

    Trott added a commit to Trott/io.js that referenced this pull request Feb 25, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: nodejs#11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    @Trott
    Copy link
    Member Author
    Trott commented Feb 25, 2017

    Landed in 4fe081d. Will make sure that #11128 and/or a subsequent PR eliminates the local instance(s) of Object.prototype.toString.call.

    @Trott Trott closed this Feb 25, 2017
    italoacasas pushed a commit to italoacasas/node that referenced this pull request Feb 25, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: nodejs#11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    @italoacasas italoacasas mentioned this pull request Feb 25, 2017
    jasnell pushed a commit that referenced this pull request Mar 7, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: #11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    jasnell pushed a commit that referenced this pull request Mar 7, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: #11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    MylesBorins pushed a commit that referenced this pull request Mar 9, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: #11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    @MylesBorins MylesBorins mentioned this pull request Mar 9, 2017
    MylesBorins pushed a commit that referenced this pull request Mar 9, 2017
    * Remove comment referring to the CommonJS Unit Testing 1.0 spec. This
      module is no longer intended to comply with that spec.
    * Remove puzzling "THIS IS NOT TESTED NOR LIKELY TO WORK OUTSIDE V8!"
      comment. No doubt, it made sense at one time.
    * Favor `===` over `==` in two places.
    
    PR-URL: #11511
    Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Anna Henningsen <anna@addaleax.net>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    @MylesBorins MylesBorins mentioned this pull request Mar 9, 2017
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Labels

    assert Issues and PRs related to the assert subsystem.

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    8 participants

    0