Skip to content

Function listings should have different or configurable term for "environment"? #529

Open
@rowanseymour

Description

@rowanseymour

Currently goflow knows nothing of RapidPro orgs and so in function docstrings we talk about the environment.. but that word won't mean much to editor users in RP when looking at those docstrings in an autocomplete or help guide... so maybe we phrase that differently, e.g. "the default date format", or replace "environment" with something else when we generate the listing?

Not even sure what the preferred term for users is.. "account", "workspace".. do users know what an "org" is ?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions