Matthew Pietz

Can squishing "mm" be made in to an option? I'm not at all fond of it and I've been reading it a lot recently (common, commit, summary, yammer, etc.) I...

I've since switched to Fira Code. It has nearly everything Monoid has that I like and it doesn't have the problem with the double-m ligature: https://github.com/tonsky/FiraCode

@aviranco That is because this library is not eslint. It's a thin wrapper around jshint and uses that library's default settings. Check the source (and `package.json`) files of this module.

You will probably want to make this change to the source file instead of just the weex output: [src/core/vdom/helpers/normalize-scoped-slots.js](https://github.com/vuejs/vue/blob/dev/src/core/vdom/helpers/normalize-scoped-slots.js)

Note that argument defaults work **only** if the value is exactly `undefined`. In your component you are setting it to `''` (an empty string) which is not `undefined`.

Would be neat to see this fixed as well. It's difficult to know which one is correct even as a human looking at Chrome Devtools :shrug:

This doesn't strike me as something that should be abstracted. I've been been able to successfully "rename" slots by using a wrapper component with manually written slot names. By doing...

I think the core of your issue though is that you might be mixing the _direction_ the slots need to be named. Take my example, `weird-slot-name` is a named slot...

Vue's hot-reload API only gets applied to `.vue` files. Use the first syntax in your example. All Vue components (functional or otherwise) should be in `.vue` files for maximum compatibility...

 To re-iterate the above comments. This is valid and shouldn't emit a warning when `vue/valid-v-slot` is on.