utilities

const customizer = console.log // returns undefined => merging is handled by `mergeAllWith`

// good
mergeAll([{ a: 1 }, { b: 2 }]) // { a: 1, b: 2 }
mergeAllWith(customizer, [{ a: 1 }, { b: 2 }]) // { a: 1, b: 2 }
// A-OK; customizer logs the following:
// undefined 2 "b" Object { a: 1, b: 2 } Object { b: 2 } undefined

// bad
mergeAll({}, { a: 1 }, { b: 2 }) // { a: 1, b: 2 }; OU

parseISO v2 documentation currently states

The previous parse implementation was renamed to parseISO.

parse v2 documentation currently states

Old parse was renamed to toDate. Now parse is a new function which parses a string using a provided format.

I think considering the sentence is to divert people who have previously been using v1 parse to the correct v2 equivalent, it only

I have marked all applicable categories:
- exception-raising bug
- [ x] visual output bug
- documentation request (i.e. "X is missing from the documentation." If instead I want to ask "how to use X?" I understand [StackOverflow#tqdm] is more appropriate)
- new feature request
[ x] I have visited the [source website], and in particular
read the [known iss

This subtitle for _.isEmpty is misleading, it kind of imply that the lodash's version does not evaluate Set or Map (which is not true), see lodash isEmpty code here.

If the ❗️is for the Native implementation, it should put on top of the Native method.

_.isEmpty
Checks if value is an empty object or collection. ❗️Note

Suggestion

Add to the Documentation a note the the following line should be added in the <head> element:

<meta name="viewport" content="width=device-width, initial-scale=1.0, shrink-to-fit=no" />

I would suggest adding it to the page Installation or to [Layout > Responsive](https://picturepan2.github.i

root@syzoj-test-vm:~/syzoj-ng-app# commitizen init cz-conventional-changelog --yarn --dev --exact
Attempting to initialize using the npm package cz-conventional-changelog
yarn add v1.19.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error Incorrect integrity when fetching from the cache
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
root@

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

who? - who wrote the p

From: https://boltons.readthedocs.io/en/latest/setutils.html#boltons.setutils.IndexedSet

As you can see, the IndexedSet is almost like a UniqueList, retaining only one copy of a given value, in the order it was first added.

This appears incorrect. Perhaps it is a remnant from an earlier version of the library?

@sesas

Some command outputs don't look great on a dark background:

Originally reported in donnemartin/saws#18 by @sesas

Share good stories. Enhancement - share link by email
Send to mobile. Enhacenement - use pushbullet api to push link to user's phone
Send to Text-to-Speech reader on android - I use " @voice " on my android to have HN articles read to me while I drive. Can we push article links using pushbullet api to your phone and to your TTS app?

My goal is to have the best documentation for each provided type.

If something is unclear in any of the types, please comment or open a PR to improve it.

Some things you could contribute:

Fix typos.
Improved description of the type.
More examples.
Provide more real-world use-cases. This helps the user understand where a type might come in handy.
Add links to relevant discu

from funcy import get_in

get_in({}, "key")  # example 1
get_in([], "key")  # example 2

In the code sample above, example 1 returns the default value because the path doesn't exist. However, example 2 fails with:

.../site-packages/funcy/colls.py in get_in(coll, path, default)
    271     for key in path:
    272         try:
--> 273             coll = coll[key]

Checklist

Please ensure the following tasks are completed before filing a bug report.

Read and understood the [Code of Conduct][code-of-conduct].
Searched for existing issues and pull requests.

Description

Description of the issue.

The following code produces an array whose shape does not match what I'd expect:

import { Assign } from 'utility-types';

type Props = { name: string; age: number; visible: boolean };
type NewProps = { age: string; other: string };

// Expect: { name: string; age: number; visible: boolean; other: string; }
type ExtendedProps = Assign<Props, NewProps>;

// Expect: { name: string; age: STRING; visible: boolean; other: string; }

In the Transform Tree example here
https://glom.readthedocs.io/en/latest/snippets.html#transform-tree

the code uses Ref

"With an arbitrary depth tree, Ref can be used to express a recursive spec."

and gives a code example

etree2tuples = Fill(Ref('ElementTree', (T.tag, Iter(Ref('ElementTree')).all())))

I'm using glom 19.10.0 and it doesn't come with Ref

from glom

Description

OpenApi/Swagger specs: https://swagger.io/docs/specification/adding-examples/

I've prepared' very simple specs, based on much more complex structure from my current project:

openapi: 3.0.0

info:
  version: development
  title: Hello World

paths:
  /hello_world/:
    get:
      operationId: api.views.hello_world
      responses:
        200:
          des

Is dotenv-expand supported? (https://github.com/motdotla/dotenv-expand)

I think not because I have attempted to add this to the env files but it doesn't work.REACT_APP_APP_VERSION=${npm_package_version}

(as per CRA docs:)
https://create-react-app.dev/docs/adding-custom-environment-variables/#expanding-environment-variables-in-env

Happy to raise a PR to add support if someone could poin

I think it would be nice to add comments to the typescript definitions, using the same documentation as is in this repository. I already did it on local but I don't have the permissions for PR's of course.

This is for the usage with VScode, following the TS doc format:
<img width="1792" alt="スクリーンショット 2019-07-25 9 57 19" src="https://user-images.githubusercontent.com/20631137/61838083-b2e8c

As windows are opened, the Wiki says they are tiled like this:

     (1)                (2)                (3)
+---+---+---+      +---+---+---+      +---+---+---+
|   |   |   |      |   |   |   |      |   |   |   |
| 1 |   |   |  ->  | 2 | 1 |   |  ->  | 3 | 2 | 1 |  ->
|   |   |   |      |   |   |   |      |   |   |   |
+---+---+---+      +---+---+---+      +---+---+---+

     (4)

utilities

Here are 1,785 public repositories matching this topic...

lodash / lodash

date-fns / date-fns

tqdm / tqdm

you-dont-need / You-Dont-Need-Lodash-Underscore

picturepan2 / spectre

Suggestion

commitizen / cz-cli

donnemartin / gitsome

mahmoud / boltons

donnemartin / saws

donnemartin / haxor-news

randyrants / sharpkeys

dwarvesf / hidden

sindresorhus / type-fest

Suor / funcy

stdlib-js / stdlib

Checklist

Description

zalo / MathUtilities

piotrwitek / utility-types

serkanyersen / ifvisible.js

mahmoud / glom

petrnohejl / Android-Templates-And-Utilities

zalando / intellij-swagger

Description

vuetifyjs / awesome-vuetify

nette / utils

Slicejack / bojler

toddbluhm / env-cmd

JBZoo / Utils

diegohaz / styled-tools

skx / sysadmin-util

lcpz / lain

Erotemic / ubelt

Utilities apps

Improve this page

Add this topic to your repo