Use demopublickey instead of real project

[nd0ut]

Description

Checklist

• Tests (if applicable)
• Documentation (if applicable)
• Changelog stub (or use conventional commit messages)

Summary by CodeRabbit

• Chores
  • Standardized the file uploader configuration across all integrations to ensure unified and reliable file upload experiences. User-facing functionality remains consistent while internal settings have been updated for improved consistency and security.

[coderabbitai]

Walkthrough

Multiple example projects across various frameworks have been updated to change the public key used in uploader configurations. In every file, the value for the pubkey attribute or prop has been updated from "a6ca334c3520777c0045" to "demopublickey". No other code or structural changes were made in these diffs.

Changes

Files	Change Summary
examples/angular-uploader/src/app/{components/file-uploader/file-uploader.component.html, views/{minimal-view.component.html, regular-view.component.html}}	Updated <uc-config> pubkey attribute from "a6ca334c3520777c0045" to "demopublickey".
examples/js-{custom-tab/index.html, custom-tab/src/index.html} examples/js-uploader/{headless.html, minimal.html, regular.html}	Updated <uc-config> pubkey attribute from "a6ca334c3520777c0045" to "demopublickey".
examples/next-uploader-adapter/pages/{minimal.js, regular.js} examples/next-uploader/pages/{minimal.js, regular.js}	Updated uploader configuration pubkey prop from "a6ca334c3520777c0045" to "demopublickey".
examples/react-uploader{,-adapter}/src/{components/FileUploader/FileUploader.tsx, views/{MinimalView.tsx, RegularView.tsx}}	Updated uploader components’ pubkey prop/attribute from "a6ca334c3520777c0045" to "demopublickey".
examples/svelte-uploader/src/{lib/FileUploader/FileUploader.svelte, routes/{minimal/+page.svelte, regular/+page.svelte}}	Updated <uc-config> pubkey attribute from "a6ca334c3520777c0045" to "demopublickey".
examples/vue-uploader/src/{components/FileUploader/FileUploader.{composition,options}.vue, views/{MinimalView.vue, RegularView.vue}}	Updated <uc-config> pubkey attribute from "a6ca334c3520777c0045" to "demopublickey".

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd07f59 and 6ea59cc.

📒 Files selected for processing (25)

• examples/angular-uploader/src/app/components/file-uploader/file-uploader.component.html (1 hunks)
• examples/angular-uploader/src/app/views/minimal-view/minimal-view.component.html (1 hunks)
• examples/angular-uploader/src/app/views/regular-view/regular-view.component.html (1 hunks)
• examples/js-custom-tab/index.html (1 hunks)
• examples/js-custom-tab/src/index.html (1 hunks)
• examples/js-uploader/headless.html (1 hunks)
• examples/js-uploader/minimal.html (1 hunks)
• examples/js-uploader/regular.html (1 hunks)
• examples/next-uploader-adapter/pages/minimal.js (1 hunks)
• examples/next-uploader-adapter/pages/regular.js (1 hunks)
• examples/next-uploader/pages/minimal.js (1 hunks)
• examples/next-uploader/pages/regular.js (1 hunks)
• examples/react-uploader-adapter/src/components/FileUploader/FileUploader.tsx (1 hunks)
• examples/react-uploader-adapter/src/views/MinimalView/MinimalView.tsx (1 hunks)
• examples/react-uploader-adapter/src/views/RegularView/RegularView.tsx (1 hunks)
• examples/react-uploader/src/components/FileUploader/FileUploader.tsx (1 hunks)
• examples/react-uploader/src/views/MinimalView/MinimalView.tsx (1 hunks)
• examples/react-uploader/src/views/RegularView/RegularView.tsx (1 hunks)
• examples/svelte-uploader/src/lib/FileUploader/FileUploader.svelte (1 hunks)
• examples/svelte-uploader/src/routes/minimal/+page.svelte (1 hunks)
• examples/svelte-uploader/src/routes/regular/+page.svelte (1 hunks)
• examples/vue-uploader/src/components/FileUploader/FileUploader.composition.vue (1 hunks)
• examples/vue-uploader/src/components/FileUploader/FileUploader.options.vue (1 hunks)
• examples/vue-uploader/src/views/MinimalView/MinimalView.vue (1 hunks)
• examples/vue-uploader/src/views/RegularView/RegularView.vue (1 hunks)

🧰 Additional context used

🧬 Code Definitions (2)

examples/next-uploader-adapter/pages/regular.js (1)

examples/next-uploader-adapter/pages/minimal.js (1)

• handleChangeEvent (11-15)

examples/next-uploader-adapter/pages/minimal.js (1)

examples/next-uploader-adapter/pages/regular.js (1)

• handleChangeEvent (12-16)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

🔇 Additional comments (25)

examples/js-custom-tab/src/index.html (1)

11-11: Appropriate change to use a demo key in the example.

Replacing the real project key with a demo key is a positive change for this example file. This helps prevent users from accidentally using a real project key and makes it clear they should replace it with their own key in real applications.

examples/js-custom-tab/index.html (1)

11-11: Appropriate change to use a demo key in the example.

Switching to "demopublickey" for this example is a good security practice. It ensures the example doesn't expose an actual project key while clearly indicating to users what value they need to replace with their own key.

examples/react-uploader/src/views/MinimalView/MinimalView.tsx (1)

40-40: Good security practice to use the demo key in examples.

Updating the React component to use "demopublickey" instead of a real project key is a positive change. This follows best practices for example code, making it clear to developers that they need to replace this value with their own public key when implementing the component.

examples/svelte-uploader/src/routes/regular/+page.svelte (1)

47-47: Correct implementation of demo key in Svelte example.

Using "demopublickey" in this Svelte component example is appropriate and consistent with the changes across other framework examples. This makes the example safer and clearer for educational purposes.

examples/svelte-uploader/src/routes/minimal/+page.svelte (1)

47-47: Good consistency in using demo key across examples.

This change to use "demopublickey" in the minimal Svelte example maintains consistency with all other example implementations. This unified approach across different frameworks makes the examples more secure and developer-friendly.

examples/react-uploader-adapter/src/views/RegularView/RegularView.tsx (1)

21-21: Good change: replaced real project key with demo key

Changing from a real project key to "demopublickey" is a good security practice for example code. This prevents potential misuse of the real project's credentials.

examples/next-uploader-adapter/pages/minimal.js (1)

24-24: Good change: replaced real project key with demo key

Appropriately replaced the real Uploadcare project key with "demopublickey" in the FileUploaderMinimal component. This change is consistent with the PR objective of using demo credentials instead of real project keys in examples.

examples/next-uploader-adapter/pages/regular.js (1)

25-25: Good change: replaced real project key with demo key

Correctly replaced the real Uploadcare project key with "demopublickey" in the FileUploaderRegular component. This aligns with the other similar changes in this PR.

examples/react-uploader/src/components/FileUploader/FileUploader.tsx (1)

135-135: Good change: replaced real project key with demo key

Appropriately updated the pubkey attribute in the uc-config component to use "demopublickey" instead of a real project key. This is particularly important for this component since it might be reused in multiple places.

examples/react-uploader-adapter/src/views/MinimalView/MinimalView.tsx (1)

20-20: Public Key Updated Successfully in React MinimalView.
The pubkey prop in the <FileUploaderMinimal> component is correctly updated to "demopublickey", fulfilling the PR’s objective.

examples/angular-uploader/src/app/views/minimal-view/minimal-view.component.html (1)

3-3: Correct Public Key Replacement in Angular Minimal View.
The <uc-config> component now uses the demo public key "demopublickey", aligning with the intended change.

examples/angular-uploader/src/app/views/regular-view/regular-view.component.html (1)

3-3: Valid Update for Angular Regular View.
The modification updates the pubkey attribute to "demopublickey" in the <uc-config> component, ensuring consistency with the new demo key.

examples/next-uploader/pages/regular.js (1)

51-51: Consistent Demo Public Key in Next.js Regular Page.
The <uc-config> component correctly sets pubkey to "demopublickey", matching the changes across the project.

examples/vue-uploader/src/views/MinimalView/MinimalView.vue (1)

39-39: Demo Public Key Applied Correctly in Vue MinimalView.
The <uc-config> component’s pubkey attribute is updated to "demopublickey", meeting the PR requirements to replace the real project key with a demo key.

examples/vue-uploader/src/views/RegularView/RegularView.vue (1)

39-39: Improved security by replacing real project key with demo key.

Changing the pubkey from a specific value to "demopublickey" is a good practice for example projects, as it prevents users from accidentally using someone else's Uploadcare account credentials.

examples/js-uploader/regular.html (1)

18-18: Correctly updated public key to use demo credentials.

The change to "demopublickey" is consistent with the PR objective and follows best practices for example code.

examples/react-uploader/src/views/RegularView/RegularView.tsx (1)

40-40: Good replacement of project-specific key with demo key.

This change aligns with the PR objective and ensures that the React example doesn't expose real project credentials.

examples/next-uploader/pages/minimal.js (1)

51-51: Properly implemented the demo public key in Next.js example.

Using "demopublickey" instead of a real project key is appropriate for this example code and consistent with changes in other framework examples.

examples/react-uploader-adapter/src/components/FileUploader/FileUploader.tsx (1)

74-74: LGTM: Using a demo key instead of a real project key

This change replaces the hardcoded API key with a generic "demopublickey" value, which is a good practice for example repositories. This prevents potential abuse of real account credentials and makes it clearer to users that they need to replace this with their own API key.

examples/js-uploader/headless.html (1)

20-20: LGTM: Consistent use of demo public key

Replacing the hardcoded API key with "demopublickey" aligns with best practices for example code. This change is consistent with the updates in other files.

examples/js-uploader/minimal.html (1)

19-19: LGTM: Using demo public key in minimal example

Good change to use a generic demo key instead of a real project key in the example code.

examples/vue-uploader/src/components/FileUploader/FileUploader.composition.vue (1)

124-124: LGTM: Consistent replacement of API key in Vue component

The change to use "demopublickey" instead of the actual API key is appropriate for example code and consistent with changes throughout the repository.

examples/angular-uploader/src/app/components/file-uploader/file-uploader.component.html (1)

17-17: Good change - replaced real project key with demo key

Replacing the actual project key with "demopublickey" improves security for example code by preventing accidental usage of real credentials in documentation and examples.

examples/svelte-uploader/src/lib/FileUploader/FileUploader.svelte (1)

114-114: Good change - using demo key instead of real key

Replacing the real project key with "demopublickey" follows best practices for example code. This prevents accidental usage of production keys in examples and demonstrates the correct integration pattern without exposing real credentials.

examples/vue-uploader/src/components/FileUploader/FileUploader.options.vue (1)

126-126: Properly replaced real project key with demo key

Consistently updating the pubkey to "demopublickey" across all examples ensures that no real credentials are exposed in the repository, while maintaining functional examples that demonstrate the correct integration pattern.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.