-
-
Notifications
You must be signed in to change notification settings - Fork 447
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
feat : add @stdlib/assert/is-nonnegative-finite #1354
feat : add @stdlib/assert/is-nonnegative-finite #1354
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋 Hi there! 👋
And thank you for opening your first pull request! We will review it shortly. 🏃 💨
lib/node_modules/@stdlib/assert/is-nonnegative-finite/README.md
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/benchmark/benchmark.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/docs/types/index.d.ts
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/docs/types/test.ts
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/docs/types/test.ts
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/primitive.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.main.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.primitive.js
Outdated
Show resolved
Hide resolved
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Yes, we generally want to explicitly use internal packages instead of native methods. This makes the dependencies of the packages explicit and what functionality they use. We also have several constructors and functions where we have or are planning to go beyond what the ECMAScript standard stipulates. The PR looks good and should be ready to merge soon; thanks for your work on this! Aside: When applying suggestions from code review, it is possible to batch them all into a single commit when doing it from the files tab. That is potentially faster than accepting them and merging them one by one. |
@Planeshifter Hi, apologies, I forgot to correct the licensing dates, I have signed and commited your suggestions. |
@marsian83 Running CI and assuming everything passes, this should be ready to land! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have a look at the CI failures; for repl.txt
, we want to ensure that we don't exceed 80 characters per line to display nicely in a terminal window. Should add a linebreak there where required.
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/primitive.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/lib/object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/README.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Hi, I signed off and commited your messages. Thanks for highlighting what I should keep in mind from next time on. I had a question though...
I did not understand what this comment is for and where should I use this. googling about this only results in "Disabling an eslint feature" but why and when would we want to do so? |
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com> Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
I just noticed your edit regarding merging commits from the file section. |
Signed-off-by: Spandan Barve <114365550+marsian83@users.noreply.github.com>
lib/node_modules/@stdlib/assert/is-nonnegative-finite/examples/index.js
Outdated
Show resolved
Hide resolved
…/index.js Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>
@marsian83 Will merge once CI passes. |
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.main.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.object.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-nonnegative-finite/test/test.object.js
Outdated
Show resolved
Hide resolved
Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>
lib/node_modules/@stdlib/assert/is-nonnegative-finite/benchmark/benchmark.js
Outdated
Show resolved
Hide resolved
…k/benchmark.js Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>
Resolves #1344 .
Description
This PR adds the package @stdlib/assert/is-nonnegative-finite.
The package implements assertion for nonnegative number except positive infinity.
Alias: isNonNegativeFinite
Related Issues
@stdlib/assert/is-nonnegative-finite
#1344Questions
I have used the
@stdlib/asset/is-finite
in order to achieve the desired result. Is this considered good practice, what are the guidelines for using internal packages, when and where is it ideal.Checklist
@stdlib-js/reviewers