Skip to content

Do we want id associated with data rather than the DO itself? #224

Closed
@bobleesj

Description

@bobleesj

Continuing our discussion from #216. @sbillinge wrote:


@bobleesj @yucongalicechen I merged this but now I am having second thoughts. Do we want the id associated with the data rather than the DO itself? In that case we should mint it in load_data and not in the constructor.

More discussion: this would go away if we don't allow an empty instance where data are loaded later. I started leaning that way because I couldn't think of a UC where we would really need that, though one would be if someone wants to load directly from a file to the DO. We could also allow that as an option in the constructor too. Can you have a think about it?

If we do mint the id on the load data function, all of our setters will have to have it insterted too.

Summary: maybe the cleanest is to mint it in the constructor as we do now but remove the ability to load data outside of the constructor (and make that method private). But aloe an option to instantiate from file by giving a file path instead of a set of arrays.

What do you think? I think I like that...

Originally posted by @sbillinge in #216 (comment)


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions