New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix GQL009 code fix formatting #3824
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #3824 +/- ##
==========================================
+ Coverage 84.47% 84.48% +0.01%
==========================================
Files 418 418
Lines 19202 19203 +1
Branches 3011 3011
==========================================
+ Hits 16220 16223 +3
+ Misses 2271 2270 -1
+ Partials 711 710 -1 ☔ View full report in Codecov by Sentry. |
lmk if I should issue a release |
This was the only problem I found with our schema. Can you check on your schema to see if there are any formatting issues? If all good, I think we can release a fix. |
I had an issue where installing GraphQL 7.7.1 broke my CI script, with the following error:
However, changing |
I think we have already talked about this problem. I'll try to take a look this weekend and see how difficult will be the fix. |
Unfortunately, I can't find any release notes for |
I'm not sure. What are the consequences if you simply reference 4.3.0.0 ? If we can reference the older version with no consequence then I would do so. One of my projects uses ASP.NET Core 2.1 (on .NET Framework) because it runs on an operating system that is not supported by .NET Core 3.1 or newer. (Technically this combination is still supported by MS, at least until the OS goes out of support.) But other users may have other reasons for using older TFMs/SDKs. |
Note that I was able to upgrade to GraphQL.NET 7.7.1 in the above scenario just fine, perhaps because the CI script installs SDKs for 2.1, 3.1, 5.0, 6.0 and 7.0. |
I'll have to test it with older versions. I have no idea what changed between versions, as MS doesn't want to manage any release notes |
The formatting was broken when lambda's parameter or body was on a different line.