Support message thread and thread member APIs #34
Conversation
cli/.env-default
Outdated
| @@ -0,0 +1,4 @@ | |||
| ELATION_BASE_URL=https://app.elationemr.com/api/2.0/ | |||
There was a problem hiding this comment.
Can we have the default vars point to the sandbox env?
| return err | ||
| } | ||
|
|
||
| spew.Dump(response) |
There was a problem hiding this comment.
That's on purpose. I don't want to write formatters for every response type.
| @@ -0,0 +1,23 @@ | |||
| module github.com/authorhealth/go-elation/cli | |||
There was a problem hiding this comment.
I don't think this needs to be a separate module
There was a problem hiding this comment.
Fair enough. My thinking was by keeping this as a separate module, it avoided making consumers of the client pull in the CLI-specific dependencies like cobra and spew.
There was a problem hiding this comment.
I think it's OK for now - maybe revisit when we feel the need to?
There was a problem hiding this comment.
Probably my lack of go-fu, but I'm getting import cycles trying to move this out of the separate package. I'm going to leave this as-is, but if you know a way to resolve this cycles, I'd be happy to refactor.
Read-only APIs for message threads and thread members.
Also adds the beginnings of a CLI tool for testing the API.