Improve the Byte array binding in the configuration source generator

Open
#116,928 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

The issue names no files or tests. Start by comparing source-generator byte[] binding with runtime reflection-based binding, then trace handling for Base64 strings, array values, and existing arrays. Done means array values append correctly, Base64 binding remains supported, and invalid values throw when BindingOption.ErrorOnUnknownConfiguration is enabled.

Written by the indexing model from the issue text.

Description

area-Extensions-Configuration source-generator

The configuration source generator currently supports binding a byte[] only from Base64-encoded strings. This issue aims to enhance byte array binding to align with the behavior of runtime reflection-based binding. The improvements should include:

  • Support for array values in configuration: Enable binding from array-style configuration values (e.g., JSON entries like byteArray: [1, 2, 3, 4]) in addition to Base64 strings.
  • Preserve and extend existing arrays: When binding to an already-initialized (non-null) byte array, the configuration values should be appended to the existing array rather than replacing it—consistent with the behavior of other array types.
  • Error handling for invalid values: If invalid configuration values are encountered, an exception should be thrown when the BindingOption.ErrorOnUnknownConfiguration flag is enabled.
Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.