It's not clear from the website's documentation, or the --help output, how to do the following equivalent curl task:

Post a raw JSON query to ElasticSearch:

curl \
    --header "Content-Type: application/json" \
    --request POST \
    --data '{ "_source": [ "restricted_countries.*" ], "query": { "match_all": {} }, "size": 1000 }' \
    'http://localhost:9200/_search'

T

Hi,

I'm looking for something like .prettierignore but on a global level, i don't want to copy that file to every new directory i make just to ignore 1 file extension which isn't supported anyway.

AFAIK this isn't supported right?

BTW the extension in this case is EJS which prettier thinks is JS and some other stuff so the best way really is to ignore .ejs as a whole.

There are grammatical errors in the English FAQ section:
https://github.com/alibaba/fastjson/wiki/FAQ(English-Version)

I propose that these grammatical errors be revised for readability.

Here are some examples below:
5. fastjson v.s. gson?
fastjson is 6 times faster than gson, here is the testing result: https://github.com/eishay/jvm-serializers/wiki/Staging-Results
fastjson is 6 tim

const XLSX = require('xlsx');

const wb = XLSX.utils.book_new();

const ws = XLSX.utils.json_to_sheet([]);

XLSX.utils.book_append_sheet(wb, ws, 'Bug sheet');

ws.A1 = { t: 's', f: 'square' };

XLSX.writeFile(wb, 'formula.ods');

The resulting .ODS file contains:

<table:table-cell table:formula="of:=square" office:value-type="string"><text:p>undefined</text:p></table

What did you do?

When I do this (from your docs):

guard let dataFromString = text.data(using: .utf8, allowLossyConversion: false) else {return} let json = JSON(data: dataFromString)

I get an error "Call can throw, but it is not marked with 'try' and the error is not handled"

I did this. I just want to confirm that is right. It worked for me.

`guard let dataFromString

Problem

Here are the types for a ts test https://github.com/paularmstrong/normalizr/blob/master/typescript-tests/entity.ts#L11

Since in the normalized entities all relationships are all id type this should be string instead of User

{
  ...
  user: string
}

I think we should patch test/CMakeLists.txt to always use -Wall -Werror on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.

@nlohmann Thoughts?

Is your feature request related to a problem

Coming from this issue: tiangolo/fastapi#817

The docs have some sections with functions using *, in the parameters.

It is explained here: https://fastapi.tiangolo.com/tutorial/path-params-numeric-validations/#order-the-parameters-as-you-need-tricks

But in other sections like: https://fastapi.tiangolo.com/tutor

Checklist

• [X ] Are you running the latest v2 release? The list of releases is here.
• [X ] Did you check the manual for your release? The v2 manual is here
• [ X] Did you perform a search about this feature? Here's the [Github guide](https://help.github.com/en/github/managing-your-wor

Your documentation shows no way to replace an objects value. Any updates to an object with:

db.get(name).find(selectors).assign(data).write()

merges the data with the existing object...not what I'd expect.

How can we replace a record without merging? Can you update your docs?

Hi, if we hope to change the order of the inline tools, how can we implement it?

For example, if we want Marker to be placed before all the other tools:

Thanks!

We are using getopt which is old school, we should upgrade to something like this: https://github.com/jarro2783/cxxopts

Currently, each argument to fx treated as an anonymous function. Here is an example:

fx 'groupBy("commit.author.name")' 'mapValues(size)' toPairs 'sortBy(1)' reverse 'take(10)' fromPairs

But this requires a lot of ' quotes. My idea is to split the argument by whitespaces . So next will be possible to write:

fx 'groupBy("commit.author.name") mapValues(size) toPairs so

I'm upgrading a build environment from python 2 to python 3 and noticed that endpoints with seeded random numbers are not returning the same values. It seems to be related to usage of randint:
https://github.com/postmanlabs/httpbin/blob/f8ec666b4d1b654e4ff6aedd356f510dcac09f83/httpbin/core.py#L1448

It seems like randint is not seed safe and it looks like only random() is: https://bugs.python.o

reproduce:

• try a schema without "properties" keyword in the playground
• and a initial-formData of type object ...

=> make sure the formData is a string to have it fixed

Warning: Failed prop type: Invalid prop `value` supplied to `TextWidget`.
    in TextWidget
    in Unknown (created by StringField)
    in StringField (created by SchemaField)
    in div (created by WrapI

Source/destinati

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

Currently, when SortMapKeys is set to true in Config, map keys are sorted using a standard alphanumeric sort. It should be possible to specify a custom map key sorting function to use, in order to prioritize certain map keys over others.

Example: Standard SortMapKeys behavior:

cfg := jsoniter.Config{
   SortMapKeys: true,
}.Froze()

m := map[string]int{
   "beta": 2,
   "alp

RFC 7515, Section 2 states:

JWS Payload
The sequence of octets to be secured -- a.k.a. the message. The
payload can contain an arbitrary sequence of octets.

This is reinforced by the example shown in Appendix A4 using a payload of the string literal Payload.

As

In the future, when Ky is more mature, we should add a comparison table to the readme. Like https://github.com/sindresorhus/got#comparison

I like the language about legacy versions and how they are are supported in https://github.com/googleapis/google-cloud-node#supported-nodejs-versions . I think we could adopt some form of it.