Skip to content

RFE JSON encoding/decoding for models #5

@jsfan3

Description

@jsfan3

Until now I used a lot PropertyBusinessObject to store the data. I'm used to create the app database using almost only PropertyBusinessObject objects. They are very convenient to exchange data with any external service, because they can seamlessly be converted to JSON and populated from JSON. Moreover, the RequestBuilder class offers method to send a PropertyBusinessObject object as body request and to fetch a PropertyBusinessObject object as the result of a request. At the moment, I consider the PropertyBusinessObject class as fundamental.

Your new CodeRAD model is very interesting, but it introduces a new way to store data in Entity objects. That makes sense, but do we lost all the advantages of the PropertyBusinessObject class? How can I use the CoreRAD concepts while maintaining all the advantages of the PropertyBusinessObject class in REST requests?

Thank you

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions