-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-applying Airtable usability changes #15015
base: master
Are you sure you want to change the base?
Changes from 1 commit
6baaf92
012d38b
460c21d
f4232f3
57f3bcd
ddc1c73
38526a1
f4f3820
cab4af5
b371f6e
b3e8b11
eaa6100
e6cdfe8
f77fae2
2d1ed37
0af5a6a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,8 +4,8 @@ import common from "../common/common.mjs"; | |
export default { | ||
key: "airtable_oauth-delete-record", | ||
name: "Delete Record", | ||
description: "Delete a record from a table by record ID. [See the documentation](https://airtable.com/developers/web/api/delete-record)", | ||
version: "0.0.7", | ||
description: "Delete a selected record from a table. [See the documentation](https://airtable.com/developers/web/api/delete-record)", | ||
version: "0.0.8", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Version inconsistency detected across Airtable OAuth components The version numbers are not consistent across the components:
Consider aligning the versions or documenting the reason for version differences. 🔗 Analysis chainVerify version consistency across Airtable OAuth components. The version bump to "0.0.8" is appropriate for the description change. However, we should ensure version consistency across related Airtable OAuth components. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check version numbers across Airtable OAuth components
# Expected: All components should have the same version number
echo "Checking version numbers in Airtable OAuth components..."
rg -g '*.mjs' '"version":\s*"[0-9]+\.[0-9]+\.[0-9]+"' components/airtable_oauth/
Length of output: 205 Script: #!/bin/bash
# Let's try a different pattern that matches the version format in the file
echo "Checking version numbers in Airtable OAuth components..."
rg -g '*.mjs' 'version: "[0-9]+\.[0-9]+\.[0-9]+"' components/airtable_oauth/
Length of output: 2498 |
||
type: "action", | ||
props: { | ||
...common.props, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,8 +4,8 @@ import { ConfigurationError } from "@pipedream/platform"; | |
export default { | ||
key: "airtable_oauth-update-field", | ||
name: "Update Field", | ||
description: "Updates an existing field in a table. [See the documentation](https://airtable.com/developers/web/api/update-field)", | ||
version: "0.0.7", | ||
description: "Update an existing field in a table. [See the documentation](https://airtable.com/developers/web/api/update-field)", | ||
version: "0.0.8", | ||
type: "action", | ||
props: { | ||
...common.props, | ||
|
@@ -27,19 +27,19 @@ export default { | |
name: { | ||
type: "string", | ||
label: "Name", | ||
description: "The name of the field", | ||
description: "The new name of the field", | ||
optional: true, | ||
}, | ||
description: { | ||
type: "string", | ||
label: "Description", | ||
description: "The description for the field", | ||
description: "The new description of the field", | ||
optional: true, | ||
}, | ||
}, | ||
async run({ $ }) { | ||
if (!this.name && !this.description) { | ||
throw new ConfigurationError("At least one of `name` or `description` must be provided."); | ||
throw new ConfigurationError("At least one of `Name` or `Description` must be provided."); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Error message formatting is inconsistent with codebase patterns Looking at the error messages across the Airtable OAuth components, the standard pattern is to use backticks only for dynamic values or technical identifiers (e.g.,
🔗 Analysis chainError message formatting improvement The updated error message now matches the UI field labels, making it more user-friendly. Let's check for consistency with other error messages in the codebase: Let me search for more error messages to get a better understanding of the error message formatting patterns. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Search for similar error messages in other Airtable OAuth components
rg -g "components/airtable_oauth/**" "must be provided" -B 2 -A 2
Length of output: 555 Script: #!/bin/bash
# Search for ConfigurationError messages in Airtable OAuth components
rg -g "components/airtable_oauth/**" "ConfigurationError" -B 1 -A 1
# Also search for error messages with backticks
rg -g "components/airtable_oauth/**" '`\w+`' -B 1 -A 1
Length of output: 6457 |
||
} | ||
|
||
const data = {}; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Add error handling for JSON parsing to match existing patterns
Looking at the codebase, other Airtable components (like create-multiple-records) implement proper JSON parsing error handling with try-catch blocks and specific error messages. The create-field action should follow the same pattern for consistency and robustness.
components/airtable_oauth/actions/create-field/create-field.mjs
: Add try-catch block for JSON parsing of options🔗 Analysis chain
Verify options parsing safety
The code safely handles options parsing, but consider adding error handling for malformed JSON input.
Consider adding try-catch for JSON parsing:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 54
Script:
Length of output: 2411