-
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
Airtable usability improvements #14691
base: master
Are you sure you want to change the base?
Changes from all commits
fc001dd
8b45320
6fa6f05
4dfe1c3
93e361b
143305e
aeeeb0b
c8b4554
cce4029
796dae1
567602a
7b0d38d
2648237
7acdbad
a660587
38f2053
e887696
f455463
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
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.6", | ||
description: "Update an existing field in a table. [See the documentation](https://airtable.com/developers/web/api/update-field)", | ||
version: "0.0.7", | ||
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 actions The version numbers are not consistent across the Airtable OAuth action files:
This inconsistency should be addressed to maintain version alignment across related components. 🔗 Analysis chainVerify version consistency across related files The version bump to "0.0.7" should be consistent across related Airtable OAuth action files. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check version numbers in related Airtable OAuth action files
# Expected: All related files should have version: "0.0.7"
echo "Checking version numbers in Airtable OAuth action files:"
rg -U 'version: "([^"]+)"' --type js components/airtable_oauth/actions/
Length of output: 196 Script: #!/bin/bash
# Let's try a different approach to find all action files and their versions
echo "Searching for action files in airtable_oauth directory:"
fd . components/airtable_oauth/actions/ -t f -e mjs
echo -e "\nChecking version strings in each file:"
for file in $(fd . components/airtable_oauth/actions/ -t f -e mjs); do
echo "=== $file ==="
cat "$file" | grep -A 1 "export default {" | grep "version"
done
Length of output: 7022 Script: #!/bin/bash
# Let's try a simpler approach with just grep to find version strings
echo "Checking version strings in all .mjs files:"
for file in components/airtable_oauth/actions/*/*.mjs; do
echo "=== $file ==="
grep -A 2 "export default" "$file"
done
Length of output: 6410 Script: #!/bin/bash
# Let's try one more time with a more specific grep pattern to find version strings
echo "Checking version strings in all .mjs files:"
for file in components/airtable_oauth/actions/*/*.mjs; do
if grep -A 5 "export default {" "$file" | grep -q "version:"; then
echo "=== $file ==="
grep -A 5 "export default {" "$file" | grep "version:"
fi
done
Length of output: 7117 |
||
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."); | ||
} | ||
|
||
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.
🛠️ Refactor suggestion
Add error handling for options parsing
The current implementation might throw unclear errors if invalid JSON is provided.
Consider adding explicit error handling:
📝 Committable suggestion