-
-
Notifications
You must be signed in to change notification settings - Fork 882
Closed
Labels
FeatureIssue or pull request for adding a new feature.Issue or pull request for adding a new feature.Good First IssueA good first issue for new contributors!A good first issue for new contributors!JavaScriptIssue involves or relates to JavaScript.Issue involves or relates to JavaScript.Needs DiscussionNeeds further discussion.Needs further discussion.RFCRequest for comments. Feature requests and proposed changes.Request for comments. Feature requests and proposed changes.UtilitiesIssue or pull request concerning general utilities.Issue or pull request concerning general utilities.difficulty: 2May require some initial design or R&D, but should be straightforward to resolve and/or implement.May require some initial design or R&D, but should be straightforward to resolve and/or implement.priority: LowLow priority concern or feature request.Low priority concern or feature request.
Description
Description
This RFC proposes adding a utility to test whether every "own" and inherited property of a provided object does not satisfy a predicate function.
This is the for-in
equivalent of @stdlib/utils/none-by
.
Package: @stdlib/utils/none-in-by
Alias: noneInBy
Related Issues
None.
Questions
No.
Other
No.
Checklist
- I have read and understood the Code of Conduct.
- Searched for existing issues and pull requests.
- The issue name begins with
RFC:
.
Metadata
Metadata
Assignees
Labels
FeatureIssue or pull request for adding a new feature.Issue or pull request for adding a new feature.Good First IssueA good first issue for new contributors!A good first issue for new contributors!JavaScriptIssue involves or relates to JavaScript.Issue involves or relates to JavaScript.Needs DiscussionNeeds further discussion.Needs further discussion.RFCRequest for comments. Feature requests and proposed changes.Request for comments. Feature requests and proposed changes.UtilitiesIssue or pull request concerning general utilities.Issue or pull request concerning general utilities.difficulty: 2May require some initial design or R&D, but should be straightforward to resolve and/or implement.May require some initial design or R&D, but should be straightforward to resolve and/or implement.priority: LowLow priority concern or feature request.Low priority concern or feature request.