pepka 0.12.2 → 0.13.0-b1

package/.circleci/config.yml

@@ -1,20 +1,20 @@
-
-version: 2
-
-jobs:
-  build:
-    working_directory: ~/test
-    docker:
-      - image: circleci/node
-    steps:
-      - checkout
-      - run:
-          name: install
-          command: npm i
-      - run:
-          name: npm test
-          command: |
-              nodejs -v
-              npm -v
-              npm run lint
+
+version: 2
+
+jobs:
+  build:
+    working_directory: ~/test
+    docker:
+      - image: circleci/node
+    steps:
+      - checkout
+      - run:
+          name: install
+          command: npm i
+      - run:
+          name: npm test
+          command: |
+              nodejs -v
+              npm -v
+              npm run lint
               npm run test:report

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,38 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-**To Reproduce**
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
-
-**Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
-
-**Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
-
-**Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
-
-**Additional context**
-Add any other context about the problem here.
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,20 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context or screenshots about the feature request here.
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

package/CODE_OF_CONDUCT.md

@@ -1,76 +1,76 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at akiliev@outlook.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at akiliev@outlook.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

package/CONTRIBUTING.md

@@ -1,3 +1,3 @@
-- Make an issue of what you want to archieve: let's be communicative.
-- Describe how does it affect API, bundle size, performance.
-- Create, write tests where possible and make a PR.
+- Make an issue of what you want to archieve: let's be communicative.
+- Describe how does it affect API, bundle size, performance.
+- Create, write tests where possible and make a PR.

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2019 Michael
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2019 Michael
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,10 +1,36 @@
-hi, api is simlimar to ramda.
-Just started to make it.
-Yes, I know, it's not a superfresh idea,
-     but I want to try, and you can switch later, due to similar api.
-It should be smallest possible ramda alternative.
-Maybe even not drop-in replacement.
-
-Later on:
-To load unsafe use smth like `import { reduce } from 'pepka/unsafe'`.
-It's faster, but mutates data.
+![image](https://user-images.githubusercontent.com/7501201/122691868-ae59f800-d23a-11eb-97fa-c0fab3cb0808.png)
+
+HI! Meet pepka - JavaScript/TypeScript functional programming utility library named after my parakeet.
+
+This lib is intended to be a functional toolkit more flexible than ramda is.
+Its' basic API is similimar to ramda's one.
+Other goals are:
+- Async pipes. They are very handy, but are not 100% pure in terms of Haskell c:
+- Most flexible types possible (Let'em be any better than crashing because of their failures. I'm currently working on full JSDocs and better basic types).
+- Tree-shakeble and smallest possible. What could be native, is native.
+- Has "quick" alternatives of most computation-heavy functions with `q` prefix which are not completely safe by fp means: most of them do mutations and it may be needed to `clone` or `cloneShallow` data in a first pipe of `compose(...)`.
+- Has basic toolbelt-types like AnyObject and AnyFunc<ReturnType?, [...args]?> etc.
+- Has some basic additinal must-have stuff that ramda does not.
+
+Full docs are coming,
+please reference ramda's ones for most operations and examples: https://ramdajs.com/docs/
+
+Basic API differences:
+- clone() clones deeply as possible any type possible.
+- cloneShallow() clones only by 1st level of folding also any type possible.
+- mergeDeep - replaces arrays.
+  - mergeDeepX - replaces its' elements with same indexes.
+  - mergeDeepAdd - adds new elements to arrays.
+- type - returns type UpperCased of anything passed to it, including classes and typed arrays.
+- mapKeys - changes existing keys and data by map or function like usual mapper.
+- explore(label)(data) - `compose(explore('the number'))(42)` results in `'the number', 42` in console passing by the data.
+- genBy(generator(index), length) - generates arrays.
+- sizeof(array or object) - counts indexes of it.
+- Aliases: mirror, reflect, echo = identity.
+- Quicks: qappend, qassoc, qreduce, qmergeDeep, qmergeDeepX, qmergeDeepAdd, qmapKeys, qfilter
+
+Async APIs:
+- composeAsync - waits for a Promise if emitted by a pipe inside it.
+- waitAll = Promise.all
+- forEachAsync - runs a handler with all elements passed in parallel.
+- forEachSerial - waits for a previous handler to resolve if Promise emitted.

package/dist/bundle.d.ts

@@ -1,13 +1,13 @@
-// Generated by dts-bundle-generator v4.0.0
+// Generated by dts-bundle-generator v5.9.0
 
 export declare type Args = any[];
-export declare const __: () => void;
+declare const __: () => void;
 export declare const curry: (fn: Function) => (...args: Args) => any;
 export declare const toLower: (s: string) => string;
 export declare const toUpper: (s: string) => string;
 export declare const type: (s: any) => any;
-export interface AnyObject {
-	[k: string]: any;
+export interface AnyObject {
+	[k: string]: any;
 }
 export declare type AnyFunc = (...args: any[]) => any;
 export declare const equals: (...args: any[]) => any;
@@ -24,23 +24,26 @@ export declare const add: (...args: any[]) => any;
 export declare const subtract: (...args: any[]) => any;
 export declare const flip: (fn: Function) => (...args: any[]) => any;
 export declare const isNil: (s: any) => boolean;
-export declare const length: (s: string | any[]) => number;
+export declare const length: (s: any[] | string) => number;
 export declare const always: <T = any>(s: T) => () => T;
 export declare const identity: (s: any) => any;
 export declare const trim: (s: string) => string;
-export declare const last: (s: string | any[]) => any;
+export declare const last: (s: any[] | string) => any;
 export declare const not: (o: boolean) => boolean;
 export declare const complement: (fn: AnyFunc) => (...args: any) => boolean | any;
-export declare const keys: (o: any[] | AnyObject) => string[];
-export declare const values: (o: any[] | AnyObject) => any[];
-export declare const toPairs: (o: any[] | AnyObject) => [string, any][];
+export declare const keys: (o: AnyObject | any[]) => string[];
+export declare const values: (o: AnyObject | any[]) => any[];
+export declare const toPairs: (o: AnyObject | any[]) => [
+	string,
+	any
+][];
 export declare const test: (...args: any[]) => any;
 export declare const tap: (...args: any[]) => any;
 export declare const append: (...args: any[]) => any;
 export declare const split: (...args: any[]) => any;
 export declare const T: (...args: any[]) => true;
 export declare const F: (...args: any[]) => false;
-export declare const sizeof: (s: string | any[] | AnyObject) => number;
+export declare const sizeof: (s: any[] | string | AnyObject) => number;
 export declare const range: (...args: any[]) => any;
 export declare const uniq: (xs: any[]) => any;
 export declare const intersection: (...args: any[]) => any;
@@ -75,7 +78,10 @@ export declare const reduce: (...args: any[]) => any;
 export declare const pickBy: (...args: any[]) => any;
 export declare const pick: (...args: any[]) => any;
 export declare const omit: (...args: any[]) => any;
-export declare const fromPairs: (pairs: [string, any][]) => any;
+export declare const fromPairs: (pairs: [
+	string,
+	any
+][]) => any;
 export declare const concat: (...args: any[]) => any;
 export declare const join: (...args: any[]) => any;
 export declare const map: (...args: any[]) => any;
@@ -113,6 +119,7 @@ export declare const qmergeDeepAdd: any;
 /** qmapKeys({ a: 'b' }, { a: 44 }) -> { b: 44 } */
 export declare const qmapKeys: (...args: any[]) => any;
 export declare const qfilter: (...args: any[]) => any;
+/** @deprecated */
 export declare const qindexOf: (...args: any[]) => any;
 export declare type StrTmpl = ((data: AnyObject) => string);
 export declare const getTmpl: (tmpl: string) => StrTmpl;