Added GraphQL type descriptions

[Akamig]

This PR resolves #1247, and "Tried but failed" to mediate #2065, but failed due to Generics of each queries in explorer.
Is there any good Idea to circumvent each IActions required by all queries?

[longfin]

@Akamig Sadly, the build is failing. 😢there are two main reasons.

1. Lint is complaining "Line must be no longer than 100 characters"
2. StandaloneSchema needs a type argument T.

• but... I don't have confidence about StandaloneSchema itself. (because I guess it's too ambigus naming)
• how about opening another PR for Provide Schema object instead of Querys #2065 ?

[Akamig]

@longfin
Alright, I changed :

• Remove StandaloneQuery and Schema, which requires .
• Shorten descriptions fit under 100 characters. Now it resolves only Explorer: GraphQL type descriptions #1247.

[longfin]

@Akamig Oops, lint is now complaining that "The parameter spans multiple lines". 😢

I guess it would be better checking dotnet build on your local env before commit & push. 🙏

[Akamig]

Maybe should I shorten description to fit under 100 characters?
but It may confuse users because of lack of additional description.

[longfin]

but It may confuse users because of lack of additional description.

It seems that make sense. then, disabling lint using #progma warning (like this) can be solution. cc @planetarium/libplanet

[pull-request-quantifier-deprecated]

This PR has 126 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Medium
Size       : +94 -32
Percentile : 45.2%

Total files changed: 3

Change summary by file extension:
.cs : +94 -32

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.