Minor thing and not related to your change but just noticed that SyntaxTrees is IEnumerable but both C# and VB represent it as ImmutableArray. So we are boxing it unnecessarily. Can't change public API but could change and use CommonSyntaxTrees.

Originally posted by @tmat in dotnet/roslyn#50615 (comment)

https://github.com/

Describe the bug

The current implementation of the authorization header parsing has (at least) the following issues:

• A value can't contain any commas
• A value can't start or end with a doublequote
• A value can't contain special characters
  • HTTP Headers only allow ASCII characters
  • There is no option to encode/decode the values (using base64 or urlencoding)
• When a value c

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

Whenever I submit a GET request to the api/public/groups endpoint, the "collections" field for each group returns "None" on every group, even if they have access to collections. I can verify that the

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/foo",
  "definitions": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "bar.json#"
        },
      },
      "required": [
        "bar"
      ],
    },
    "title": "foo"
  }
}

Running quicktype CLI with this Schema produces

Error

Documentation for hidewindow configuration is missing.

Suggested solution

• Add documentation to XML and YAML config documentation
• Update the YAML schema so that it includes documentation for the field

In reference to this discussion, I am filing a request to have Textview support scrollbars for very large results that are outside the area/window.

Please let me know if there are any additional details I should provide in this issue.