Skip to content
This repository was archived by the owner on Nov 14, 2024. It is now read-only.
This repository was archived by the owner on Nov 14, 2024. It is now read-only.

Consider using the Newtonsoft custom converters instead of dynamic types #29

Open
Open
Consider using the Newtonsoft custom converters instead of dynamic types#29
Assignees
stijnmoreels
Labels
enhancementNew feature or requestfeature-suggestionAll issues related suggestion of a new feature. These are nice to haves but not customer requestsspecs-requiredAll issues where the specifications are still being defined and implementation should be halted
Milestone
v0.2.0
@stijnmoreels

Description

@stijnmoreels
stijnmoreels
opened on Jun 5, 2020

Is your feature request related to a problem? Please describe.
Consider using the Newtonsoft custom converters instead of dynamic types

Describe the solution you'd like
It should be investigated if we could/should use custom JSON converters instead of using dynamic's.

Additional context

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestfeature-suggestionAll issues related suggestion of a new feature. These are nice to haves but not customer requestsspecs-requiredAll issues where the specifications are still being defined and implementation should be halted

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions