quickbase / quickbase-cli Goto Github PK

https://github.com/spf13/cobra#version-flag

See https://github.com/mitchellh/gon#gon---cli-and-go-library-for-macos-notarization and https://developer.apple.com/developer-id/ for the context.

Goreleaser can help us: https://goreleaser.com/customization/sign/

The qbclient package is a full-fledged SDK for Go. We should add a README to allow developer to use the package independent of the CLI tool.

Right new, we use the Makefile to build artifacts and such. Could https://goreleaser.com/ help us?

Right now, the CLI tool only supports dbid's for the --table-id option. It would be great if we supported aliases, e.g., _DBID_CHILD, or the table name.

I have tables in Quickbase with many, many columns. If I do a records query on more than 20 columns or an export of a table with more than 20 columns I get this error:
ERROR message="error decoding response" error="" transid=ca7682t0hqaa7jn29590 code=500
Where is this coming from and is there any workaround?
It seems to be a hard columns (fields) limit. I get an error even if I limit the number of rows retrieved.

For example, if a field is added to default reports and you run field update without setting --add-to-reports, the field will be removed from the default reports. Omitting the option should not change the field setting.

Implement a command like the following:

quickbase-cli field create-summary [CHILD_TABLE_ID] [RELATIONSHIP_ID] --field-id [FIELD_ID] --accumulation-type SUM

For example, if we want to return fields 6 through 10, we have to set the following option: --select 6,7,8,9,10,11,12. Wouldn't it be great if we could accomplish the same result by setting --select 6:12?

When runningquickbase-cli records query and selecting an attachment field, an error decoding response error is returned.

The Cobra library has built-in shell completions. We should implement the ability to create shell completions. If we figure out #3 , then we should auto-add the completions.

The --formula option accepts a string for a formula, but this can be limiting as formulas can be hundreds of lines long. The goal is to be able to define a formula in a file and be able to point to it to upload the formula.

See https://docs.microsoft.com/en-us/windows/package-manager/winget/.

We will prioritize Scoop (#6) but should keep an eye on the progress of winget to see if we should add support for it as well.

v0.2.4 and v0.2.5 are unable to run on some mac versions:

Likely issue:

upx/upx#424

See cpliakas/cliutil#6

It would be helpful to have import/export commands that can perform these operations with batching and delays to take care of some of the plumbing that needs to be implemented to do these operations at scale.

fmt.Sprint will display exponents for large values. We just want to print the data as it is returned bu Quickbase.

strconv.FormatFloat(v.Float64, 'f', -1, 64) should do the trick.

Although we should keep the basic usage and command syntax in the README, we should move the specific examples to the Wiki, as the REAME is getting unwieldy.

This is gross:

func NewQuickbaseClient(cfg *qbclient.ConfigFileProfile) *qbclient.Client {
	v := viper.New()
	v.SetDefault(qbclient.OptionRealmHostname, cfg.RealmHostname)
	v.SetDefault(qbclient.OptionUserToken, cfg.UserToken)
	v.SetDefault(qbclient.OptionTemporaryToken, cfg.TemporaryToken)
	return qbclient.New(qbclient.NewConfig(v))
}

We can do better.

We have to make two API calls during a records insert, one to get the schema metadata so that we can appropriately serialize the command line data, and the second to insert the records. If you use the -d option to dump what is sent/response over the wide, the response for both the GET /v1/fields?tableId={bdis} and POST /v1/recordsAPI calls are appended to the same dump file. They should be separate files.

See https://github.com/lukesampson/scoop.

Related to #5.

The --label option is required for the field update command, which it shouldn't be.

It would be great to have a command that reads a configuration file and deploy formulas stored in files.

Json output is useful when you want machines to read the data, but it would be great to visualize the data as a table when you want to inspect the data as a human.

Currently, we use the validation error message directly from the go-validate package. The error message are not in the least bit friendly to the user.

For example, omitting the required --accumulation-type option results in the following message:

2021/01/21 00:38:53.235142 ERROR message="Bad request" error="/summaryFields/0 required key [accumulationType] not found" transid=c04cq73rbdg75vn6ti8g code=400

If should just say "accumulation-type option required".

cpliakas/cliutil#4 will make this easier.

We are not capturing the line errors in qbclient.InsertRecordsOutputMetadata. This omission is a bug.

• https://developer.quickbase.com/operation/getFieldsUsage
• https://developer.quickbase.com/operation/getFieldUsage

t would be helpful to support using field labels in place of field IDs. For example, My Field instead of 7.

Example error:

2021/02/03 17:35:48.373042 ERROR message="error decoding response" error="" transid=c0ddtsrrbdg3tq2rbih0 code=500

The --skip and --top options do not seem to work.

See https://github.com/goreleaser/nfpm.

Goreleaser can help us: https://goreleaser.com/customization/nfpm/

The goal is to make it easier to install and maintain the CLI tool on OSX.

See https://github.com/Homebrew/brew/blob/master/docs/How-to-Create-and-Maintain-a-Tap.md

NewValueFromString should support file attachments by assuming the string is a file path and reading the data of the file into a base64 encoded string.

We shouldn't need to pass Output to Output.handleError handler implementations. This is probably an artifact of old code. It isn't hurting anything, but it is a little confusing.