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: #1038
- Status: Further investigation and more details required.
- 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: #1451
- Status: More details required.
- Issue: #682
- Status: "Nice to have" but significant investment in terms of infrastructure/planning.
- Issue: #829
- Status: More consideration and customer feedback required.
- Issue: #803
- Status: Resources are alive as long as the application is anyway.
- Issue: #500
- Status: No customer requests for this yet; can implement when reqiured.
- Issue: #110
- Status: Ideally, protoc should do this. Massive work item, no funding right now.
- Issue: #1784
- Status: Both proposed options need server changes in some form or other.