Skip to content

invalid syntax when a TMPL variable is undefined #424

@joe-p

Description

@joe-p

Currently when a TMPL variable is undefined the client will throw this error from algod when trying to compile:

URLTokenBaseHTTPError: Network request error. Received status 400 (Bad Request): 1 error: 6:58: strconv.ParseUint: parsing "TMPL_NFD_REGISTRY_APP_ID": invalid syntax

Instead, we should check the constant blocks for any TMPL_ and generate a more human-friendly error about the undefined TMPL variable.

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