Aru Sahni

For reference, here's where I left off during my snap experimentation: ```yaml name: git-req version: git summary: Check out merge requests from your GitLab/GitHub hosted repos with ease! description: |...

This should have been fixed with #14, right?

Thanks for your response, @samscott89! I'm looking forward to seeing where this project goes! :popcorn:

I, too, am experiencing this issue. At close zoom levels, with very large numbers of documents, my radii explode, basically leaving a large red overlay over empty portions of the...

I think it's going to be a lot easier to go Py3-only nowadays. Regarding @unuseless's comment, [it looks like GAE now supports Python 3.7](https://cloud.google.com/appengine/docs/the-appengine-environments).

I'm still getting this error. Was the pull request merged in?

The version in the Arch repo pushes a `lenovo_fix.service`.

Given the node-sass CLI doesn't appear to support passing CLI options to the importer, would you see this being accomplished via environment variables? e.g., `SASS_IMPORTER_OPTIONS="--package-keys style,main,sass" node-sass --importer path/to/node-sass-magic-importer/cli.js`?

I had the same issue. My issue was that I was using objects for options, and had set `:track-by="value"` while also having a `value` prop on my component. I solved...

@sainnhe I'm assuming this is under the `languageserver` section of coc-settings? If so, having installed the plugin in VS Code, I'm getting the following error with your snippet: ``` [coc.nvim]...