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

This fixes issue #issue 2651 #2656

Draft
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

MathioLucas
Copy link

@MathioLucas MathioLucas commented Dec 5, 2024

This fixes issue #issue 2651
a quick summary for file changes and additions
avatars.less

Replaced hardcoded avatar types with a single CSS class using variables.
avatars.json

Updated .typeXX classes to .vignette with a data-type attribute.

avatarLoader.js
Create this new file to dynamically assign avatar images.

Import avatarLoader.js.

To Automate the creation of avatars.json during build time.

new file to map avatar types to their image paths.
Instead of manually specifying a background-image for each type, the avatar image is assigned using JavaScript and the avatars.json file.
Handles dynamic assignment of avatar images using the avatars.json configuration.
Automatically generates avatars.json at build time by scanning the avatars folder.
Confirms avatars.json is generated correctly and included in the deployed build directory.
Copy link

vercel bot commented Dec 5, 2024

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

Name Status Preview Updated (UTC)
ancientbeast ❌ Failed (Inspect) Dec 5, 2024 11:19pm

@DreadKnight
Copy link
Member

Heya! Thanks for the PR. Seems it fails to build. Also, please always ping issues using hashtag and then number: #2651

package.json Show resolved Hide resolved
@DreadKnight
Copy link
Member

@MathioLucas I've opened a review. "package.json" is the faulty file, very obvious problem there 🐻

@DreadKnight
Copy link
Member

@MathioLucas PR titles should be more descriptive, something like "auto-generated unit avatar grid at build time" in this case, as even if properly tagging the issue there, it won't be clickable (like it can be in description). Plus it's way more useful when stuff is reviewed and very importantly, when generating the list of changes for a new version release.

@DreadKnight DreadKnight marked this pull request as draft December 8, 2024 03:45
@DreadKnight
Copy link
Member

@MathioLucas Hey! Still waiting for a fix on this one 🐻

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