Kenichi Kamiya

https://github.com/soutaro/rbs-inline/commit/cade2727220015514af1d5be4125c4b60d0aeb1b#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R9 > This gem is a prototype for testing. We plan to merge this feature to rbs-gem and deprecate rbs-inline gem after that. https://github.com/ruby/rbs/issues?q=is%3Aissue+is%3Aopen+%22rbs-inline%22 Looks like no issues in upstream...

Original problem is not yet resolved

I suspect that backend does not correctly return JSON object... 🤔 https://github.com/pankona/hashira/blob/fec942f373cfa12c63c6af4c275e1f2c3c169b9e/hashira-web/functions/func.go

@EPMatt Hi, I personally don't use ts-node. However, the example repository looks like it's working. Could you check https://github.com/kachick/example-octokit-graphql-schema-968 and the GitHub action result? https://github.com/kachick/example-octokit-graphql-schema-968/actions/runs/12499600836/job/34874808718 tested dependencies and the configuration...

Pinned with ts-node 10.8.1 and octokit/graphql-schema v15.4.2 https://github.com/kachick/example-octokit-graphql-schema-968/blob/5638d82b0abc51e40af8a25c4229506d756bb5ea/package.json#L1-L10 https://github.com/kachick/example-octokit-graphql-schema-968/actions/runs/12499807260/job/34875251485

@elbrenn thank you for updating this PR by [merging the main branch](https://github.com/actions/languageservices/pull/79/commits/3df66511a9d73282941e70cf71d32d6119e9543c). Should I take any further action regarding this PR?

@nebuk89 I noticed that https://github.com/actions/languageservices/pull/191 clarified that this repository no longer accepts PRs except from GitHub members. Could you also clarify what will happen with existing PRs? I understand if...

nixpkgs packged in https://github.com/NixOS/nixpkgs/pull/306835 and updated to jv 0.7.0 in https://github.com/NixOS/nixpkgs/pull/384225

Yeah, I agree this is a trade-off problem, and I respect the project's decisions on how to handle these cases. Thanks for your consideration. I'm already using a global typos...

Ah, my apologies for the confusing wording. When I wrote `file-specific`, I meant to say `file-type-specific`. Likely `ignore wdth for specific file types (.css, .html)`.