Chapter in question: https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch2.md#template-literals

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

The max-classes-per-file rule is enabled in rules/best-practices.js but there is no mention of this requirement in the docs. If this is a best practice, I'd like to know why.

Bug report

Feature Request

• I would like to work on this feature!
  • If needs be, I can look into it

Is your feature request related to a problem? Please describe.

The JSX spec [1][2] lists } and > as invalid JSX text characters.

JSXTextCharacter :

• SourceCh

🐛 Bug Report

I tried passing --open to the parcel src/index.html command, but nothing happened. This feature works perfectly in the latest stable parcel-bundler package.

🎛 Configuration (package.json)

{
  "scripts": {
    "start": "parcel src/index.html --open"
  }
}

🤔 Expected Behavior

Parcel should open http://localhost:1234 in my default web brow

When I check during update Korean translate of 33-js-concepts, I found some typo like below.

https://eslint.org/docs/rules/func-call-spacing

When calling a function, developers may insert optional whitespace between the function’s name and the parentheses that invoke it.

Option: "never" (default) disallows space between the function name and the opening parenthesis.

Examples of incorrect code for this rule with the default "never" option:

/*eslint func-call-spacin

Describe the bug
The default _limit for the find() is currently fixed to 100. I can't understand why the team picked it is 100? why wouldn't be 10 or 50?.

If some one needed to fetch default 50 records for all end point of find(), at-least he have to edit all request URL or needed to override the current find() handle.

This may not be a bug for the team, but for best framework we need t

The contributing guidelines need to be fixed immediately. Issue creation guideline specially. We need to enforce adding label as one of the behaviours while creating a new issue.

cc- @tsov

Would you be interested by an interactive documentation/blog post like this ones:

• http://blog.klipse.tech/javascript/2016/12/19/es2017-sleep.html
• http://blog.klipse.tech/javascript/2016/12/19/es2017-entries.html

Disclaimer: I'm the author of the klipse plugin.

I set

{
        test: /\.svg$/,
        loader: 'svg-sprite-loader',
        include: [resolve('./src/renderer/icons')],
        exclude: [resolve('./src/renderer/icons')],
        options: {
          symbolId: 'icon-[name]'
        }
      },
      {
        test: /\.(png|jpe?g|gif|svg)(\?.*)?$/,
        loader: 'url-loader',
        exclude: [resolve('./src/renderer/ic

Some of the current background image selections have low contrast against the text or could be better quality images that better relate to selected verticals. This may be irrelevant if we decide to remove the image altogether.

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing issue
• I've read the docs and followed them (if applicable)
• This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots

can you provide documentation for triggers / events handling like copy, cut, paste , merge cell, changing color for specific cell etc. thanks @myliang

• I'm submitting a ...

  • bug report
  • feature request

• What is the motivation / use case for changing the behavior?

https://github.com/epicmaxco/vuestic-admin/blob/2a64ca23d0b462e5b4cbdf03570a45ccb69850cb/src/components/admin/AppLayout.vue#L15

I suggest the specific layout styles should be defined in routes instead of the main layout.
Any ideas?

This is a reminder for loadimpact/k6#1162

configDir is a copy of os.UserConfigDir to support pre go1.12, it should be removed and use os.ConfigDir directly from go1.13 onward.

Hi there,

The https://glidejs.com/docs/extending page sends a 404.
The dead link can be found on the https://glidejs.com/docs/ in the "Extended section".
Here is a screenshot:

Cordially,
Cyril

• bizcharts Version: any
• Platform or react version: any
• Mini Showcase(like screenshots):
• CodePen Link: https://codepen.io/anon/pen/zgwdRE

retro step:

1. click "toggle tooltip", tooltip change to sticky mode.
2. click "toggle tooltip", tooltip should recover default config, but it not.

Original issue in Nuxt.js repository:

• esm() breaks console.*() functions in esm-styled nuxt.config.js · Issue #6808 · nuxt/nuxt.js

Currently we have the following tests:

[esm/compiler-tests.mjs at a3b8290074ccd2a708ed9b985a2f89d4f4cdd026 · standard-things/esm](https://github.com/standard-things/esm/blob/a3b8290074ccd2a708ed9b985a2f89d4f4c