Skip to content

Overload etag/etagger (and other potential pairs, e.g.: key/keyer) #5

@mikeboers

Description

@mikeboers

If we restrict the types that are allowed to be used as etags (and/or user-specified keys, see #4), then we could allow either a scalar etag or a function to create said etag to be passed via the same etag kwarg.

Potential set of types could be:

  • strings
  • ints
  • bools
  • None
  • tuples of these

Basically, hashable builtin types.

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