Now that Prettier 2.0 has been released with its improved CLI, I think we should add a section do the docs showing a recommended example setup.

1. Recommend using an editor extension that lets you run Prettier from your editor. Link to popular extensions. Maybe add some tips on how to configure for example prettier-vscode.
2. Recommend adding an empty ({}) .prettierrc.json to signify to edit

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

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
}

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?

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

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

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.

When I have a malformed JSON (e.g. an extra or a missing comma)
When the validation fails, I get:
$ resume export --theme jsonresume-theme-eloquent resume.html
Done! Find your new .html resume at:
resume.html

No mention of an error, and the created HTML file does not display correctly.

When I fix the errors, after running
$ jsonlint-php resume.json
to see all the errors in my JSON,

The current example in https://github.com/benjamine/jsondiffpatch/blob/master/docs/formatters.md does not trigger html arrows display.

This is the closest I've came up with to make it work :

  var delta = jsondiffpatch.diff(left, right);
  // left is optional, if specified unchanged values will be visible too

  var el = document.getElementById('the-diff');

 el.innerHTML = jso

This seems to be a fairly popular request as it has been asked about several times over the years, so I wonder if it would be worth adding as a feature to tabulator in some form.

Some examples of the request:
olifolkerd/tabulator#527
olifolkerd/tabulator#1511
olifolkerd/tabulator#1759

I also opened (and answered

Request type

• Please close this issue, I accidentally submitted it without adding any details
• New documentation
• Correction or update

Details

Burried in the Formal Syntax is <media-or> that allows a list of media rules to use the or keyword. As I understand this change was added in [CSS Conditional Rules Module Level 3](https

It would be useful to standardize and document the responses for each operation, such as the status code, response body, etc.

Status codes

See https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

Here are some suggested examples:

Success

Fail

Code | Description | Us

General information

• json-editor version: 2.2.1

Chrome and Firefox

options:

 theme:'bootstrap4', 

in case it matters

Expected behavior

When I click "notes", I expect the checkbox to be checked

Actual behavior

Not

🐛 Bug Report

For types array the items key is not mandatory by the standard, but it is needed by fast-json-stringify.
We should set a default instead

To Reproduce

var fastJsonStringify = require("fast-json-stringify")
const str = fastJsonStringify({
  "type": "object",
  "properties": {
    "foo": {
      "type": "array"
       // , items: { type: 'string' } // unco

This tools is great, we can define and validate various config from file, env, cli arg... and we can even put a short doc on each field.

But what if I want to display a clear and concise doc reference on a website on a cli usage?

Should this package be able to handle that? If not, is it compatible with other packages doing that need?

Thanks

It's more natural to click the actual value instead of icon next to it for editing purposes. Would it be hard to implement?