Skip to content

API is not ergonomic #62

@felixfbecker

Description

@felixfbecker

It seems like the API is purely a generated gRPC client. This makes it very unergonomic for JavaScript in many places:

  • None of the classes have constructors. For example, I can't pass the value directly to new Value(), instead I have to call value.setStringVal('abc'). One would expect an API more around object literals rather than getter and setter methods
  • The API allows contradictory state. For example, what happens when I call both setStringVal() and setIntVal()?
  • Some methods are confusingly named - e.g. setSetJson()
  • There are no docblocks on any methods
  • Some types are completely unclear how to use - e.g. setGeoVal() takes a string or a UInt8Array.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions