Skip to content

Should #create! raise an ArgumentError if the instance already has an id? #38

@cjcolvar

Description

@cjcolvar

What should happen if #create! is called on an encode instance that already has an id? Should it raise an ArgumentError or should it submit that to the adapter in an attempt to assign that id in the external encoding service? Personally, I would expect that the external service would always assign an id and that an encode instance with an id should raise an exception.

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