Releases: coda/packs-sdk
Releases · coda/packs-sdk
Release 1.5.1
Fixed
- Fixed an error with property options for object properties.
Release 1.5.0
Added
- Started tracking the raw keys of object properties internally as
originalKey
.
Release 1.4.1
Added
- Added
AuthenticationType.MultiHeaderToken
, allowing you to specify multiple headers to include in each request. Previously, if the API you were using required multiple headers, you would need to useAuthenticationType.Custom
.
Release 1.4.0
Added
- Added the command
coda extensions
to the CLI for installing developer extensions that help with building Packs. Currently it only supports Visual Studio Code (coda extensions vscode
), creating a code snippets file which provides the same slash commands as the Pack Studio.
Changed
- Using the empty string as a
tokenPrefix
with OAuth2 authentication will result in no prefix being used in theAuthentication
header. Previously, the empty string would be treated the same asundefined
which would lead to the default prefix ofBearer
being used. Note that this change took effect for live packs on April 28, 2023 independently of the SDK version; in this SDK version the behavior changed only here in the CLI execution simulator (thecoda execute
command). - Breaking Change Removed the "autocomplete" property from EmailSchema. It wasn't useful in practice and we want to free up the name "autocomplete" on BaseSchema for better purposes.
Release 1.3.4
Fixed
- Fixed an issue with
placeholder
property being stripped out of thePropertyIdentifierDetails
schema.
Release 1.3.3
Changed
- Switched the node package manager from yarn to pnpm. This only affects developers contributing changes to the packs-sdk repo.
- Added optional
placeholder
property toPropertyIdentifierDetails
definition as a default value for Pack card titles, subtitles, and snippets when value is empty.
Fixed
- Fixed an issue where the fetcher was converting XML responses to JSON even when setting
isBinaryResponse: true
. - Fixed an issue where the authentication type
AWSAccessKey
wasn't generating correct signatures when used locally.
Release 1.3.0
Added
- Added an
--apiToken
argument to theclone
,create
,link
,release
, andupload
CLI commands. This makes it easier to use the CLI in a CI/CD environment where the API token is passed as an environment variable (GitHub Actions, etc).
Changed
- Updated
PrecannedDateRange
to match the date range picker in the Coda UI: addedLast90Days
,Last180Days
,Last365Days
,Next90Days
,Next180Days
,Next365Days
,Last7AndNext7Days
,Last30AndNext30Days
, deprecatedLast3Months
,Last6Months
,Next3Months
, andNext6Months
, and removedThisWeekStart
,ThisMonthStart
, andThisYearStart
, which never actually worked.
Fixed
- Fixed an issue where
coda execute ... --vm=false
wasn't compatible with Node version 19+ (Cannot set property crypto of #<Object> which has only a getter
).
Release 1.2.3
[1.2.3] - 2022-12-13
Added
- Added a new formula parameter type
Markdown
as an alternative toHTML
for formatted text.
Release 1.2.2
Added
- Added an option
credentialsLocation
toOAuth2Authentication
, to specify how the client ID and secret should be passed during the token exchange. The defaultAutomatic
should be sufficient for most OAuth2 providers.
Release 1.2.1
Added
- Added an option
ignoreRedirects
toFetchRequest
, if you do not want the fetcher to follow HTTP 301/302 redirects and instead want to observe such a response and examine the redirect URL directly (by reading theLocation
header) instead of following it.