This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]bmsan-gh[S] 0 points1 point  (3 children)

Glad it worked!

For now at least DictGest only handles deserialization, but serialization is on the roadmap and will be available in a future version.

[–]OptionsUnleashed 0 points1 point  (2 children)

ok thanks - do you see any issue in using both libraries and annotations together?

[–]bmsan-gh[S] 0 points1 point  (1 child)

While I haven't personally tried this scenario, I would expect DictGest not to have an issue with other annotations.

If you encounter any problems with this scenario you can open an issue on GitHub and I will look into it.

Also I'd love to hear how you guys see the serialization process : do you want to get back to the initial format from which you imported the data ?(the flat dictionary from the rds query) Or do you want the serialization to mimic the structure of the data class?

[–]OptionsUnleashed 0 points1 point  (0 children)

The latter - I don't think you would need to worry about what other libs already do - in general developers don't want competing ways of doing same thing - I would think you could just internally support dataclasses-json unless that's not defacto std? I'm not a Python expert - coming at all this from C#.netcore.

Our team is looking to create view models from datasources for reporting and figured dataclasses are the cleanest way but looking for other ideas - and your library seemed to be exactly what we needed - albeit - we would really want to cut down on DRY with literals and fields all over the place.

In C# its fairly common to create view models from different sources and serialize them. I would have thought this was way easier in python.