Some Planner options are always strings. For example, it's now impossible to create a plan, bucket, or whatever with name 123. CLI will interpret these values as number.
Let's enforce the string type for options that should always be interpreted as a string.
For all planner plan, planner bucket, planner roster, planner task commands, let's interpret following options always as string:
bucket:
- id
- name
- planId
- planTitle
- ownerGroupName
- orderHint
- newName
- rosterId (option coming soon)
plan:
- id
- title
- ownerGroupName
- rosterId
- newTitle
task:
- id
- title
- planId
- planTitle
- ownerGroupName
- bucketId
- bucketName
- description
- assigneePriority
- orderHint
- taskId
- alias
Some Planner options are always strings. For example, it's now impossible to create a plan, bucket, or whatever with name
123. CLI will interpret these values as number.Let's enforce the
stringtype for options that should always be interpreted as a string.For all
planner plan,planner bucket,planner roster,planner taskcommands, let's interpret following options always as string:bucket:
plan:
task: