Start adding API examples for different rest api and upload api endpoints #170
Conversation
WalkthroughThe recent updates encompass a broad range of REST API functionalities for managing files, groups, webhooks, and metadata using the Uploadcare API. These changes streamline user interactions by facilitating file operations, metadata updates, webhook handling, and file storage efficiently across various scripts. Changes
Poem
TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" | ||
|
|
||
| puts Uploadcare::Webhook.delete('https://yourwebhook.com') |
There was a problem hiding this comment.
Parameterize the webhook URL to enhance flexibility and security.
- puts Uploadcare::Webhook.delete('https://yourwebhook.com')
+ webhook_url = 'https://yourwebhook.com' # This should be configurable
+ puts Uploadcare::Webhook.delete(webhook_url)Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| puts Uploadcare::Webhook.delete('https://yourwebhook.com') | |
| webhook_url = 'https://yourwebhook.com' # This should be configurable | |
| puts Uploadcare::Webhook.delete(webhook_url) |
Consider adding error handling for the webhook deletion operation.
+ begin
puts Uploadcare::Webhook.delete(webhook_url)
+ rescue => e
+ puts "Failed to delete webhook: #{e.message}"
+ endCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| puts Uploadcare::Webhook.delete('https://yourwebhook.com') | |
| begin | |
| puts Uploadcare::Webhook.delete('https://yourwebhook.com') | |
| rescue => e | |
| puts "Failed to delete webhook: #{e.message}" | |
| end |
api-samples/rest_api/get_webhooks.rb
Outdated
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that API keys are not hardcoded in production code.
It's crucial to avoid hardcoding sensitive information like API keys in your source code. Consider using environment variables or a secure vault solution to manage these credentials securely.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that API keys are not hardcoded in production code.
As previously mentioned, avoid hardcoding sensitive information like API keys in your source code. Use environment variables or a secure vault solution to manage these credentials securely.
api-samples/rest_api/get_groups.rb
Outdated
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that API keys are not hardcoded in production code.
Again, it's important to avoid hardcoding sensitive information like API keys in your source code. Use environment variables or a secure vault solution to manage these credentials securely.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that API keys are not hardcoded in production code.
As with the other files, avoid hardcoding sensitive information like API keys in your source code. Use environment variables or a secure vault solution to manage these credentials securely.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
api-samples/upload_api/post_base.rb
Outdated
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in the scripts.
As before, avoid hardcoding sensitive information like API keys in your scripts. Use environment variables or a secure vault solution instead.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in the scripts.
To emphasize, avoid hardcoding sensitive information like API keys in your scripts. Use environment variables or a secure vault solution instead.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in the scripts.
Once again, avoid hardcoding sensitive information like API keys in your scripts. Use environment variables or a secure vault solution instead.
api-samples/rest_api/get_files.rb
Outdated
| require 'uploadcare' | ||
| Uploadcare.config.public_key = "YOUR_PUBLIC_KEY" | ||
| Uploadcare.config.secret_key = "YOUR_SECRET_KEY" |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in the scripts.
As a final reminder, avoid hardcoding sensitive information like API keys in your scripts. Use environment variables or a secure vault solution instead.
There was a problem hiding this comment.
Actionable comments posted: 37
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (43)
- .rubocop.yml (1 hunks)
- api_examples/rest_api/delete_files_storage.rb (1 hunks)
- api_examples/rest_api/delete_files_uuid_metadata_key.rb (1 hunks)
- api_examples/rest_api/delete_files_uuid_storage.rb (1 hunks)
- api_examples/rest_api/delete_groups_uuid.rb (1 hunks)
- api_examples/rest_api/delete_webhooks_unsubscribe.rb (1 hunks)
- api_examples/rest_api/get_addons_aws_rekognition_detect_labels_execute_status.rb (1 hunks)
- api_examples/rest_api/get_addons_aws_rekognition_detect_moderation_labels_execute_status.rb (1 hunks)
- api_examples/rest_api/get_addons_remove_bg_execute_status.rb (1 hunks)
- api_examples/rest_api/get_addons_uc_clamav_virus_scan_execute_status.rb (1 hunks)
- api_examples/rest_api/get_convert_document_status_token.rb (1 hunks)
- api_examples/rest_api/get_convert_document_uuid.rb (1 hunks)
- api_examples/rest_api/get_convert_video_status_token.rb (1 hunks)
- api_examples/rest_api/get_files.rb (1 hunks)
- api_examples/rest_api/get_files_uuid.rb (1 hunks)
- api_examples/rest_api/get_files_uuid_metadata.rb (1 hunks)
- api_examples/rest_api/get_files_uuid_metadata_key.rb (1 hunks)
- api_examples/rest_api/get_groups.rb (1 hunks)
- api_examples/rest_api/get_groups_uuid.rb (1 hunks)
- api_examples/rest_api/get_project.rb (1 hunks)
- api_examples/rest_api/get_webhooks.rb (1 hunks)
- api_examples/rest_api/post_addons_aws_rekognition_detect_labels_execute.rb (1 hunks)
- api_examples/rest_api/post_addons_aws_rekognition_detect_moderation_labels_execute.rb (1 hunks)
- api_examples/rest_api/post_addons_remove_bg_execute.rb (1 hunks)
- api_examples/rest_api/post_addons_uc_clamav_virus_scan_execute.rb (1 hunks)
- api_examples/rest_api/post_convert_document.rb (1 hunks)
- api_examples/rest_api/post_convert_video.rb (1 hunks)
- api_examples/rest_api/post_files_local_copy.rb (1 hunks)
- api_examples/rest_api/post_files_remote_copy.rb (1 hunks)
- api_examples/rest_api/post_webhooks.rb (1 hunks)
- api_examples/rest_api/put_files_storage.rb (1 hunks)
- api_examples/rest_api/put_files_uuid_metadata_key.rb (1 hunks)
- api_examples/rest_api/put_files_uuid_storage.rb (1 hunks)
- api_examples/rest_api/put_webhooks_id.rb (1 hunks)
- api_examples/upload_api/get_from_url_status.rb (1 hunks)
- api_examples/upload_api/get_group_info.rb (1 hunks)
- api_examples/upload_api/get_info.rb (1 hunks)
- api_examples/upload_api/post_base.rb (1 hunks)
- api_examples/upload_api/post_from_url.rb (1 hunks)
- api_examples/upload_api/post_group.rb (1 hunks)
- api_examples/upload_api/post_multipart_complete.rb (1 hunks)
- api_examples/upload_api/post_multipart_start.rb (1 hunks)
- api_examples/upload_api/put_presigned_url_x.rb (1 hunks)
Files skipped from review due to trivial changes (7)
- .rubocop.yml
- api_examples/rest_api/get_addons_uc_clamav_virus_scan_execute_status.rb
- api_examples/rest_api/get_files_uuid.rb
- api_examples/rest_api/post_addons_uc_clamav_virus_scan_execute.rb
- api_examples/rest_api/put_files_storage.rb
- api_examples/upload_api/post_group.rb
- api_examples/upload_api/put_presigned_url_x.rb
Additional comments not posted (27)
api_examples/rest_api/get_project.rb (1)
5-6: Good use of API to fetch and display project information.This script effectively demonstrates how to retrieve and inspect project information using the Uploadcare API. It follows good practices in terms of API usage and code clarity.
api_examples/rest_api/get_webhooks.rb (1)
5-6: LGTM! Simple and effective use of the API to list webhooks.api_examples/rest_api/get_groups.rb (1)
5-6: LGTM! Effective use of the API to list groups with a limit.api_examples/rest_api/get_groups_uuid.rb (1)
5-6: LGTM! Correct usage of the API to retrieve group information by UUID.api_examples/rest_api/get_convert_document_uuid.rb (1)
5-6: LGTM! Proper use of the API to retrieve document conversion information.api_examples/rest_api/post_addons_remove_bg_execute.rb (1)
5-6: LGTM! Effective demonstration of using the API to remove background from an image.api_examples/upload_api/post_base.rb (1)
5-6: LGTM! Correct implementation of file upload functionality.api_examples/rest_api/get_files_uuid_metadata.rb (1)
5-6: LGTM! Proper use of the API to retrieve specific metadata for a file.api_examples/rest_api/get_files_uuid_metadata_key.rb (1)
5-6: LGTM! Effective demonstration of retrieving all metadata for a file.api_examples/rest_api/post_addons_aws_rekognition_detect_labels_execute.rb (1)
6-6: Verify the method name and parameters.api_examples/upload_api/get_info.rb (1)
6-7: Check the output format and ensure it meets the requirements.api_examples/upload_api/get_group_info.rb (1)
6-7: Check the output format and ensure it meets the requirements.api_examples/upload_api/get_from_url_status.rb (1)
6-6: Check the methodget_upload_from_url_statusfor correct implementation and error handling.api_examples/upload_api/post_from_url.rb (1)
6-6: Verify theuploadmethod's parameters and ensure they are correctly used.Verification successful
The search results from the
rgcommand have provided us with various definitions of theuploadmethod across different contexts within the Uploadcare module. Notably, the methodupload(file, options = {})inlib/uploadcare/client/uploader_client.rbis relevant to our review. This method internally callsupload_many([file], options), indicating that it accepts a file and an options hash, which is flexible and can include various key-value pairs.The original code snippet from the review:
Uploadcare::Uploader.upload(source_url, store: 'auto')This matches with the flexible
optionsparameter in the method definition found. Thestore: 'auto'part of the snippet is a part of the options hash, which is consistent with the method's ability to accept various options.Given this information, it appears that the usage of the
uploadmethod in the provided code snippet is correct, as it aligns with the method's definition allowing for flexible options.Conclusion:
Theuploadmethod's parameters are being used correctly in the provided code snippet, as the method definition supports a flexible options hash, which includes thestorekey used in the snippet.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the parameters of the `upload` method. # Test: Search for the method definition and its parameters. Expect: Correct usage of parameters. ast-grep --lang ruby --pattern $'module Uploadcare { module Uploader { def upload($_, store: $_) { $$$ } } }'Length of output: 473
Script:
#!/bin/bash # Description: Broaden the search for the `upload` method in the Uploadcare module to capture any variations in its definition. # Using rg to search for the method definition in Ruby files. rg --glob '*.rb' 'def upload' -A 3 -B 2Length of output: 4679
api_examples/rest_api/post_addons_aws_rekognition_detect_moderation_labels_execute.rb (1)
6-6: Verify the method name and parameters.Verification successful
The method
ws_rekognition_detect_moderation_labelsdoes indeed exist within theUploadcarecodebase, specifically underlib/uploadcare/client/addons_client.rb. The method accepts a single parameteruuid, which aligns with the usage shown in the provided code snippet from the fileapi_examples/rest_api/post_addons_aws_rekognition_detect_moderation_labels_execute.rb.Given this information, the method name and parameters have been verified as correctly implemented and used.
- File:
lib/uploadcare/client/addons_client.rb
- Method:
ws_rekognition_detect_moderation_labels(uuid)Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the method `ws_rekognition_detect_moderation_labels` exists and is correctly implemented. # Test: Search for the method definition. Expect: Method definition with correct parameters. ast-grep --lang ruby --pattern $'module Uploadcare { module Addons { def ws_rekognition_detect_moderation_labels($_) { $$$ } } }'Length of output: 493
Script:
#!/bin/bash # Description: Broaden the search to verify the existence of the method `ws_rekognition_detect_moderation_labels` in any context within the Ruby files. # Test: Search for the method definition in a broader context. rg --glob '*.rb' 'def ws_rekognition_detect_moderation_labels'Length of output: 261
api_examples/rest_api/get_files.rb (1)
5-6: Check thefile_listmethod for correct implementation and performance considerations.Verification successful
The
file_listmethod in theUploadcare::Client::FileListClientclass has been successfully located and its implementation details are now clear. The method accepts a hash of options which can include parameters likeremoved,stored,limit,ordering, andfrom. These options are then converted into a query string and used to make a GET request to the/files/endpoint.Analysis of Performance Considerations:
- Query Construction: The method constructs a query string based on the provided options. This is efficient as it allows for flexible API calls without hardcoding parameters.
- HTTP GET Request: The method uses a GET request to fetch data, which is appropriate for retrieving information without modifying server state.
- Use of URI Encoding: The method uses
URI.encode_www_formfor encoding the query parameters, ensuring that the URL is correctly formatted and safe to transmit over the network.Conclusion:
The method is implemented correctly with respect to its functionality. It efficiently handles the construction of query parameters and makes appropriate use of network requests. There are no obvious performance issues with the method as it stands; it is designed to be flexible and efficient for its intended use case of fetching file lists with various filters.
Given this analysis, the original review comment concerning the correct implementation and performance considerations of the
file_listmethod has been addressed.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the method `file_list` exists and is optimized for performance. # Test: Search for the method definition. Expect: Correct implementation and performance considerations. ast-grep --lang ruby --pattern $'module Uploadcare { module FileList { def file_list(stored: $_, removed: $_, limit: $_) { $$$ } } }'Length of output: 497
Script:
#!/bin/bash # Description: Re-verify the existence and implementation of the `file_list` method in the Uploadcare module. # Using ast-grep with a refined pattern ast-grep --lang ruby --pattern $'module Uploadcare { module FileList { def file_list($$$) { $$$ } } }' # Using rg to search for the method definition in Ruby files rg "def file_list" --glob '*.rb'Length of output: 577
Script:
#!/bin/bash # Description: Display the contents of the file_list method for manual inspection. # Using cat to display the relevant lines from the file where the method is defined cat lib/uploadcare/client/file_list_client.rbLength of output: 1490
api_examples/rest_api/put_files_uuid_metadata_key.rb (1)
8-8: Verify theupdatemethod's parameters and ensure they are correctly used.Verification successful
The search results from the
rgcommand have successfully located the definition of theupdatemethod within theUploadcare::Client::FileMetadataClientclass. The method signature isdef update(uuid, key, value), which matches the usage in the provided code snippet from the fileapi_examples/rest_api/put_files_uuid_metadata_key.rb:Uploadcare::FileMetadata.update(uuid, key, value)This confirms that the parameters
uuid,key, andvalueare used correctly according to the method definition found in the codebase.Conclusion:
Theupdatemethod's parameters are correctly used in the provided code snippet as per the method definition found in the codebase.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the parameters of the `update` method. # Test: Search for the method definition and its parameters. Expect: Correct usage of parameters. ast-grep --lang ruby --pattern $'module Uploadcare { module FileMetadata { def update($_, $_, $_) { $$$ } } }'Length of output: 474
Script:
#!/bin/bash # Description: Search for the 'update' method in the 'FileMetadata' module using ripgrep. # Search for the method definition in Ruby files to ensure the correct usage of parameters. rg --glob '*.rb' 'def update' -C 5Length of output: 2673
api_examples/rest_api/get_addons_remove_bg_execute_status.rb (1)
6-7: Good use of the API to check the status of the background removal operation.api_examples/rest_api/delete_files_storage.rb (1)
6-6: Ensure proper error handling when deleting files.Verification successful
The examination of the
batch_deletemethod and its associated test cases reveals that error handling is indeed implemented. The method inlib/uploadcare/client/file_list_client.rbdelegates error handling to therequest_deletemethod by passing the necessary parameters. This suggests that any error handling would be managed by therequest_deletemethod or the underlying network layer.Furthermore, the test cases in
spec/uploadcare/entity/file_list_spec.rbandspec/uploadcare/client/file_list_client_spec.rbinclude scenarios where thebatch_deletemethod is tested with nonexistent UUIDs, and the responses are checked for problems, indicating that the method can handle error scenarios effectively.Given this information, it can be concluded that the implementation of error handling around the
batch_deletemethod is adequate.Error Handling Verified for File Deletion
- The
batch_deletemethod inlib/uploadcare/client/file_list_client.rbuses existing infrastructure for error handling.- Test cases in
spec/uploadcare/entity/file_list_spec.rbandspec/uploadcare/client/file_list_client_spec.rbconfirm that error scenarios are effectively handled.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that error handling is implemented for batch file deletion. # Test: Search for error handling around `batch_delete` method. rg --type ruby $'batch_delete'Length of output: 1345
Script:
#!/bin/bash # Description: Inspect the implementation of `batch_delete` and related error handling in the codebase. # Check the implementation of `batch_delete` in file_list_client.rb cat lib/uploadcare/client/file_list_client.rb # Check the test cases that handle failure scenarios in file_list_spec.rb and file_list_client_spec.rb cat spec/uploadcare/entity/file_list_spec.rb cat spec/uploadcare/client/file_list_client_spec.rbLength of output: 6695
api_examples/rest_api/post_files_local_copy.rb (1)
6-7: Good use of the API to copy files locally with storage options.api_examples/rest_api/get_addons_aws_rekognition_detect_labels_execute_status.rb (1)
6-7: Good use of the API to check the status of label detection operations.api_examples/rest_api/post_webhooks.rb (1)
10-10: Good use of the API to create webhooks with specified options.api_examples/rest_api/get_addons_aws_rekognition_detect_moderation_labels_execute_status.rb (1)
6-7: Good use of the API to check the status of moderation label detection operations.api_examples/rest_api/post_convert_document.rb (1)
7-7: Good use of the API to convert documents with specified options.api_examples/upload_api/post_multipart_complete.rb (1)
8-8: Good use of the API for multipart uploads.api_examples/rest_api/post_convert_video.rb (1)
5-11: Validate the UUID and parameters for video conversion to ensure they are correct and secure.api_examples/rest_api/post_files_remote_copy.rb (1)
5-8: Validate the source UUID and target storage to ensure they are correct and secure.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive information such as public and secret keys are not hardcoded in the source code.
Consider using environment variables or a secure vault to store and retrieve these keys dynamically.
| source_file = File.open('image.png') | ||
| Uploadcare::Uploader.upload(source_file, store: 'auto') |
There was a problem hiding this comment.
Tip
Codebase Verification
The shell script execution confirmed that the file image.png does not exist or is not readable in the current directory from which the script was run. This directly supports the review comment suggesting that the existence and permissions of the source file should be validated before attempting to upload it. This is crucial to prevent runtime errors in the application.
Given this information, the review comment is validated as it correctly identifies a potential issue in the code that could lead to an exception if not handled properly.
File image.png is missing or lacks read permissions
The verification process confirmed that the file image.png does not exist or is not readable in the current directory. This supports the need for implementing a check in the code to ensure the file's existence and readability before attempting to upload it. This is a necessary step to enhance the robustness of the application.
- Recommended Action: Implement a check in the
post_multipart_start.rbscript to verify the existence and readability ofimage.pngbefore proceeding with the upload process.
Analysis chain
Validate the existence and permissions of the source file before attempting to upload.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check if 'image.png' exists and has appropriate permissions.
# Test: Check file existence and permissions. Expect: File exists and is readable.
if [ -f "image.png" ] && [ -r "image.png" ]; then
echo "File exists and is readable."
else
echo "File does not exist or is not readable."
fi
Length of output: 111
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure key management system to handle API keys securely.
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive information such as public and secret keys are not hardcoded in the source code.
Consider using environment variables or a secure vault to store and retrieve these keys dynamically.
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' | ||
|
|
||
| puts Uploadcare::Webhook.delete('https://yourwebhook.com') |
There was a problem hiding this comment.
Consider parameterizing the webhook URL.
Hardcoding the webhook URL (https://yourwebhook.com) in the script limits its reusability and could potentially expose sensitive endpoints if shared publicly. Consider parameterizing this value to enhance security and flexibility.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
| require 'uploadcare' | ||
| Uploadcare.config.public_key = 'YOUR_PUBLIC_KEY' | ||
| Uploadcare.config.secret_key = 'YOUR_SECRET_KEY' |
There was a problem hiding this comment.
Ensure that sensitive keys are not hardcoded in production code.
Consider using environment variables or a secure vault to store API keys to enhance security.
Description
Start adding API examples for different rest API and upload API endpoints
Checklist
Summary by CodeRabbit
New Features
Enhancements