ATS DTOs improvement ideas
Open
Nobody has claimed this yet.
needs-area-label
triage:bot-seen
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 201
Description
Some suggestions that came up while creating custom DTOs
- We may want to create a custom class representing any JSON primitive type (string, int, number, bool) so we can use it in properties and dictionaries. In C# we would use
objectbut it's too vague so not compatible with DTOs right now. Using such a type would allow us to limit what polyglot apphosts can use in such properties (serializable values). - The same way we may be able to also serialize object handles. Since we can detect them from the polyglot app, we may be able to serialize them the same way we do in the RPC communication.
c.f. discussion https://github.com/microsoft/aspire/pull/17878#discussion_r3352639098
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion linked from the issue, especially the referenced pull request discussion, to understand the DTO constraints and existing RPC serialization behavior. The issue needs a defined scope and design decision for primitive-value types and object-handle serialization before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100