Yuto Ito
Yuto Ito
## Problem When highlight link is nested, caw.vim fails to uncomment. ## Cause In the current implementation, `s:comment_detectable.has_syntax` uses synIDtrans to get the terminal syntax name. If the terminal syntax...
I want to call `textobj#python#function_select_[ai]` and `textobj#python#class_select_[ai]` in one mapping. First. call `function_select_[ai]` If `function_select_[ai]` fail, call `class_select_[ai]`
I will make this plugin deprecated. because the solargraph supported Language Server Protocol. LSP is a server-client protocol. Neovim has its client([LanguageClient-neovim](https://github.com/autozimu/LanguageClient-neovim)). If the solargraph work with LanguageClient-neovim. I will...
Please install 1.18.0 until this problem is solved. `gem install solargraph -v 0.18.0`
I separated `deoplete-solargraph` and` solargraph-utils.py` from the viewpoint of maintainability and modularity. This made development very easy, but for users it would be troublesome to add more packages to manage....
Hi! thank you for awesome library! I found below bug. When deleted the data in backend, plugin-graphql doesn't remove data from Vuex store on secondary fetch. ### Reproduce step As...
バグはタイトル通りです。 変数を設定すればいいだけの話ですが念の為報告しておきます。
* controllerでStandardErrorをキャッチするのを辞めたい * controllerから `render_error` (独自) を消したい * 現状ではlocationsとpathが空 * 全てのエラーに `extensions` で `request_id` をつけたい executeでStandardErrorを全てキャッチして `raise GraphQL::ExecutionError.new("Something went wrong", extensions: { "code" => "BROKEN" })` のようにしたい。 unexpected errorはこれでハンドリングできる。 https://graphql-ruby.org/errors/error_handling#add-error-handlers...