Skip to content
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

Add customizable placeholder feature to Avatar component #1433

Closed
wants to merge 4 commits into from

Conversation

itsusif
Copy link

@itsusif itsusif commented Sep 14, 2024

This pull request introduces the fallbackSrc prop to the Avatar component, allowing for customizable placeholder images when the main image fails to load. It also updates the documentation with examples of the new feature and revises the Svelte code to handle fallback image display.


Status:

  • Not Completed
  • Completed

Checks:

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • I have checked the page with https://validator.unl.edu/
  • All the tests have passed
  • My pull request is based on the latest commit (not the npm version).

Additional Information:

This update enhances the Avatar component by providing an option to specify a fallback image. It is useful for scenarios where a default placeholder image is preferred if the main image fails to load.

Summary by CodeRabbit

  • New Features

    • Introduced a fallback image feature for the Avatar component, enhancing user experience when the primary image fails to load.
    • Added customizable placeholder support, allowing users to specify a custom fallback image.
  • Documentation

    • Updated documentation for the Avatar component to include new features and improve clarity on usage.

- Introduced `fallbackSrc` prop for customizable placeholder images.
- Updated documentation with examples for new feature.
- Revised Svelte code to handle fallback image display.
Copy link

vercel bot commented Sep 14, 2024

@itsusif is attempting to deploy a commit to the Themesberg Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Sep 14, 2024

Walkthrough

The changes enhance the Avatar.svelte component by adding support for a fallback image when the primary image fails to load. Two new properties, fallbackSrc and onError, are introduced to manage this functionality. Additionally, the documentation in avatar.md has been updated to reflect these changes, including minor formatting adjustments and a new section on the customizable placeholder feature. These modifications improve the component's usability and clarity without altering its existing logic.

Changes

File Change Summary
src/lib/avatar/Avatar.svelte Added support for a fallback image with new properties fallbackSrc and onError.
src/routes/docs/components/avatar.md Updated documentation with formatting adjustments and added a section for the customizable placeholder feature.

Poem

In the meadow where avatars play,
A fallback image brightens the day.
When the main one fails, don’t you fret,
A custom placeholder, your best bet!
So hop along, let worries cease,
With smooth transitions, find your peace! 🐇✨

Tip

OpenAI O1 model for chat
  • We have deployed OpenAI's latest O1 model for chat.
  • OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
  • Please share any feedback with us in the discussions post.

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 235523d and 6b46e6b.

Files selected for processing (2)
  • src/lib/avatar/Avatar.svelte (4 hunks)
  • src/routes/docs/components/avatar.md (7 hunks)
Additional comments not posted (10)
src/lib/avatar/Avatar.svelte (6)

6-7: LGTM!

The new exported properties fallbackSrc and onError are correctly typed, have appropriate default values, and include clear comments explaining their purpose. These changes align with the PR objective of adding support for a fallback image.


28-35: LGTM!

The updates to the avatarClass reactive variable correctly integrate the new props using the twMerge function. The changes maintain the existing logic while incorporating the new functionality seamlessly.


37-38: LGTM!

The introduction of the imageSrc reactive variable is a good design choice. It provides a single source of truth for the image source, making it easier to manage the fallback mechanism and maintain a cleaner separation of concerns.


40-45: LGTM!

The handleError function correctly implements the fallback mechanism by setting imageSrc to fallbackSrc when an error occurs and onError is true. The function signature is correctly typed, ensuring type safety. This change aligns with the PR objective of providing a smoother user experience when the primary image fails to load.


50-56: LGTM!

The changes to the img element correctly integrate the fallback mechanism into the rendering flow. Using imageSrc instead of src ensures that the fallback image is displayed when necessary, and binding the on:error event to handleError triggers the fallback mechanism when an error occurs. These changes align with the PR objective of providing a smoother user experience.


70-76: LGTM!

The changes to the img element in the else block correctly integrate the fallback mechanism into the rendering flow. Using imageSrc instead of src ensures that the fallback image is displayed when necessary, and binding the on:error event to handleError triggers the fallback mechanism when an error occurs. These changes maintain consistency with the previous img element and align with the PR objective.

src/routes/docs/components/avatar.md (4)

12-15: LGTM!

The addition of semicolons for consistency is a good practice and improves code readability.


47-47: LGTM!

The text refinement improves clarity and readability.


104-104: LGTM!

The text refinement improves clarity and readability.


Line range hint 185-223: Excellent addition of the Customizable Placeholder feature!

The new section provides clear instructions on how to use the fallbackSrc prop to specify a custom placeholder image. The example code demonstrates the usage correctly.

This feature enhances the usability of the Avatar component by allowing developers to provide a fallback image when the main avatar image fails to load.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 resolve resolve all the CodeRabbit review comments.
  • @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.

@itsusif itsusif changed the title Avatar Add customizable placeholder feature to Avatar component Sep 14, 2024
Copy link

vercel bot commented Sep 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
flowbite-svelte ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 21, 2024 2:06pm

@shinokada
Copy link
Collaborator

shinokada commented Sep 21, 2024

Why can't we use

<!-- Default avatar placeholder SVG -->
<svg class="w-full h-full {rounded ? 'rounded' : 'rounded-full'}" fill="currentColor" viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
<path fill-rule="evenodd" d="M8 9a3 3 0 100-6 3 3 0 000 6zm-7 9a7 7 0 1114 0H3z" clip-rule="evenodd" />
</svg>
to replace the default avatar?

{#if fallbackSrc}
 <img
    {alt}
    src={imageSrc}
   class={rounded ? 'rounded' : 'rounded-full'}
 />
{:else}
<!-- default avatar placeholder -->
    <svg class="w-full h-full {rounded ? 'rounded' : 'rounded-full'}" fill="currentColor" viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
       <path fill-rule="evenodd" d="M8 9a3 3 0 100-6 3 3 0 000 6zm-7 9a7 7 0 1114 0H3z" clip-rule="evenodd" />
    </svg>
{/if}

@itsusif
Copy link
Author

itsusif commented Sep 22, 2024

Why can't we use

<!-- Default avatar placeholder SVG -->
<svg class="w-full h-full {rounded ? 'rounded' : 'rounded-full'}" fill="currentColor" viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
<path fill-rule="evenodd" d="M8 9a3 3 0 100-6 3 3 0 000 6zm-7 9a7 7 0 1114 0H3z" clip-rule="evenodd" />
</svg>

to replace the default avatar?

{#if fallbackSrc}
 <img
    {alt}
    src={imageSrc}
   class={rounded ? 'rounded' : 'rounded-full'}
 />
{:else}
<!-- default avatar placeholder -->
    <svg class="w-full h-full {rounded ? 'rounded' : 'rounded-full'}" fill="currentColor" viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
       <path fill-rule="evenodd" d="M8 9a3 3 0 100-6 3 3 0 000 6zm-7 9a7 7 0 1114 0H3z" clip-rule="evenodd" />
    </svg>
{/if}

Hi @shinokada,

Thanks for the suggestion!

In the current implementation, the component already manages the case where the default SVG avatar is used if fallbackSrc isn’t provided or src fails to load. Here’s how it works:

  1. If src loads successfully: The image is displayed.
  2. If src fails and fallbackSrc is provided (with onError set to true): The fallbackSrc image is used.
  3. If fallbackSrc is missing or set to null: The default SVG avatar is displayed.

This gives users the flexibility to either specify a custom fallback or rely on the default SVG.

Relevant code:

Let me know if this works or if you have any other suggestions!

@shinokada
Copy link
Collaborator

If a user adds a wrong image path, the image won't be displayed.
Am I missing something here?

<Avatar src="/wrong/path/to/image.webp" fallbackSrc="/images/fallback-picture.webp" />

image

@shinokada
Copy link
Collaborator

Also why when a user add a fallbackSrc, it won't be displayed?

<Avatar src="/images/profile-picture-3.webp" fallbackSrc="/images/fallback-picture.webp" />
<Avatar fallbackSrc="/images/profile-picture-3.webp" />
<Avatar src="/wrong/path/to/image.webp" fallbackSrc="/images/profile-picture-3.webp" />

image

@shinokada
Copy link
Collaborator

I close the PR for now. Thank you for your contribution.

@shinokada shinokada closed this Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants