Skip to content
This repository was archived by the owner on Jul 23, 2019. It is now read-only.
This repository was archived by the owner on Jul 23, 2019. It is now read-only.

Suggestion: Don't use overloaded Point and Range terms in API #102

@lee-dohm

Description

@lee-dohm

One thing that we ran into problems with the original API were the Point and Range classes. Since the browser APIs contain classes named the same, we ran into naming collisions causing issues for those attempting to use the Atom API. I figured I would record this piece of tribal knowledge here so that we can avoid it in Xray.

Suggestions

Alternatives for Point:

  • Location
  • Coordinate
  • Position

Alternatives for Range:

  • Span
  • Section
  • Bounds
  • Dimension
  • Limits

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