This file is used to keep track of feature requests that we may want to come back to at some point, but aren't on our immediate radar. Using this single document is simpler than keeping all the corresponding issues open, but we'll reopen the issue if we revisit the request and want to put work into it.
- Issue: #1818
- Status: For consideration when everything is very stable. Making something part of the public API is a big decision.
- Issue: #1709
- Status: Further investigation required. We already have some analysis in the form of custom Roslyn analyzers.
- Issue: #682
- Status: "Nice to have" but significant investment in terms of infrastructure/planning.
- Issue: #829
- Status: More consideration and customer feedback required.
- Issue: #500
- Status: No customer requests for this yet; can implement when required.
- Issue: #2182
- Status: We don't have a good solution for where to log these. Won't affect clients directly.
- Issue: #2166
- Status: We haven't received interest for this feature.
Diagnostics: Including information stored in System.Exception.Data in the Stackdriver Error Reporting entry.
- Issue: #2738
- Status: The original requester never confirmed whether our approach solved their use case or not.
- Issue: #2513
- Status: Waiting for more users to request this, so we can gather suitable requirements.
- Issue: #2163
- Status: Waiting for demand on this. To be reconsidered if we decide to merge the existing Diagnostics libraries into one
- Issue: #3335
- Status: Waiting for demand on this. We have some ideas, but little customer input.
- Issue: #5384
- Status: Semantic breaking change. To be considered for a major version if and when we plan for one.
Log4Net: Provide an opt in mechanism to remove (null)
valued labels, which come from unset properties.
- Issue: #5325
- Status: Waiting for more demand on this so we can have better requirements.
- Issue #9250
- Status: Unlikely to implement in Google.Cloud.Storage.V1. Should be considered from the start for any future Storage library - with a greenfield API surface and without the implementation constraints of Google.Apis, we're much more likely to be able to do this cleanly.