tomi / fromfrom Goto Github PK

The devDependency css-loader was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

css-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚨 The automated release from the release branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Are there any particular reasons why the development version of ts is set to es2015 instead of es2018?

Doesn't seem to work when I do this

The devDependency ts-jest was updated from 24.0.0 to 24.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

I've come from C# and like your project. Couldn't find much out there (in TypeScript) like it - mystified by that! Would love to see just a simple fromRange(start:number, end:number) and maybe fromInfinite() to get me started. Or is there already some way to do that?

The devDependency file-loader was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

file-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency ts-node was updated from 8.0.2 to 8.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The synchronous transformation of data has already been solved elegantly with transducers. You can refer to:

• https://jlongster.com/Transducers.js--A-JavaScript-Library-for-Transformation-of-Data
• https://github.com/thi-ng/umbrella/tree/master/packages/transducers (a more complete transducers library)

Transducers apply equally to iterators and observable. I don't mean this to belittle your effort, I rather want to attract the attention on prior art and not reinventing (redebugging) the wheel.

One possible advantage of your approach may be the typings. Transducers are pretty hard to type both accurately and concisely.

The devDependency webpack-dev-server was updated from 3.3.0 to 3.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-dev-server is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rollup was updated from 1.4.1 to 1.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi there,

This library looks interesting and helpful!

I just want to know how chaining works here regarding with the performance. Since chaining creates a temporary array w/c affects performance. That is why using transducer on a massive list is better.

Any thoughts?

A first-time contributor here! I would love to open up a pull request and implement some stuff! Looks like the except function might be the lowest hanging fruit, so I'd love to take a stab at it.

On the lodash documentation page, the without function uses a signature like this:

const items = _.without(array, ...items);

How about something like this?

const squares = from([1, 2, 3])
  .except(2) // or maybe name it `without` instead?
  .map(e => e * e)
  .toArray();

The devDependency replace-in-file was updated from 3.4.3 to 3.4.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

replace-in-file is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I think there is a small mistake on the type for toObject function when a selector is introduced.

Currently it's this:

toObject(keySelectorFn: MapFn<TItem, string>): StringKeyedObject<TItem>;
toObject(keySelectorFn: MapFn<TItem, number>): NumberKeyedObject<TItem>;
toObject<TElement>(keySelectorFn: MapFn<TItem, string>, elementSelectorFn: MapFn<TItem, TElement>): StringKeyedObject<TItem>;
toObject<TElement>(keySelectorFn: MapFn<TItem, number>, elementSelectorFn: MapFn<TItem, TElement>): NumberKeyedObject<TItem>;

I think the ones with the element selector should have a keyed object of type TElement.

The devDependency copy-webpack-plugin was updated from 5.0.0 to 5.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

copy-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency highlight.js was updated from 9.14.2 to 9.15.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

highlight.js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I don't know how to formulate the question correctly or if it makes sense.

I love the library, but the first thing that came to mind was if it were possible to use function composition with it. Export the transforms as standalone functions waiting for an Iterator and be able to compose transformations. Is this out of the scope?

Example (comopse):

// from the main example
import { compose, filter, sortBy } from 'fromfrom/transforms';

const activeSortedByName = compose(
  sortByDescending(user => user.age),
  filter(user => user.active)
);

const result = activeSortedByName(users).toArray();

Example (pipe):

// from the main example
import { pipe, filter, sortBy, toArray } from 'fromfrom/transforms';

const activeSortedByName = pipe(
  filter(user => user.active),
  sortByDescending(user => user.age),
  toArray
);

const result = activeSortedByName(users);

Hi, I was wondering if there are any plans to add basic aggregate operators, i.e sum, avg, min, max, etc, for a whole collection or as part of a groupBy operation?

Alternatively do you have any suggestions on how to efficiently implement per group aggregation? So far I've come up with this (from your playground examples), but perhaps there's a better approach:

import { from } from "fromfrom";
import data from "./data";

const result = from(data)
  .groupBy(u => u.country)
  .toObject(
    g => g.key,
    g => ({
      items: g.items,
      count: g.items.length,
      sum: g.items.reduce((s, i) => s + i.score, 0),
      avg: g.items.reduce((s, i) => s + i.score, 0) / g.items.length,
      min: g.items.reduce((s, i) => Math.min(s, i.score), Infinity),
      max: g.items.reduce((s, i) => Math.max(s, i.score), -Infinity),
    })
  );

P.s: In case you are interested, I've pitted a number of similar libs and fromfrom consistently comes on top in terms of perf (atleast in Firefox, other browsers are temperamental): https://codesandbox.io/s/angry-wind-zu0gj

The fact that it is also the smallest in size, 100% coverage, type-safe, is admirable.

Hi,
Thanks for making this library - it looks promising as I'm just creating a project that could use extensive search/filter/morph of data. I'm not a pro dev, so below will be few points from that perspective

1. I went through documentation but it's written in TS often without practical use examples. This makes it hard to figure out how am I supposed to use each transform. Would you consider providing code examples in documentation akin to how, for example, Lodash does theirs for every transformation?

2. I've noticed your usage examples on Playground show working with flat data. If I have some objects nested few levels deep, would you expect me to manually destructure object tree and then feed each branch to fromfrom transforms? Ideally I would like to filter the entire object tree in one operation (see example mockup object https://pastebin.com/icBgpV5c), and for example if I want to do .filter(color: "green") and get as output new object with only branches that end with a color: "green" (expected: https://pastebin.com/a8qUnPp0). Could you give example of how you envision a workflow of operations when working with nested data like this? I'm most interested in .filter .sort .groupBy .find .pick

3. How do you envision us doing operations with multiple parameters/conditions? Let's say I want to filter by two colours and have my filter parameters stored in separate array. Would doing it like this be the best way?:

const fndcolours = ["red", "green"];

from(data)
 .filter(user => fndcolours.includes(user.color))
  .toArray();

Thanks again

Not all methods of Sequence have a usage example in the documentation. We should add usage examples with an @example JSDoc annotation to all methods. This way they end up in the generated API documentation automatically.