Skip to content

missing error info in evaluateExpression #43

@n0izn0iz

Description

@n0izn0iz

currently, evaluateExpression throws a "constant" error here if the query failed, where the gnokey cli returns the actual go error

this is a pain for dev where you have to run a modified client or the cli to know the actual error message

Metadata

Metadata

Assignees

No one assigned

    Labels

    hacktoberfestGood issues for hacktoberfest

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions