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

Fix styleguide #353

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

Fix styleguide #353

wants to merge 5 commits into from

Conversation

NishilJ
Copy link
Contributor

@NishilJ NishilJ commented Feb 18, 2025

Overview

Fixes to styleguideist config so that it runs and removal of unnecessary dependencies.

Other Notes

The styleguide/documentation js bundle can be locally viewed using npx styleguidist server and can be built using npx styleguidist build which will output to the styleguide folder. This build folder was removed from git. Certain component folder/file names may need to be changed in the future so that the casing matches with the corresponding component name, file name, and folder name.

Copy link

vercel bot commented Feb 18, 2025

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

Name Status Preview Comments Updated (UTC)
utd-trends ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 21, 2025 1:31am

Copy link
Contributor

@AbhiramTadepalli AbhiramTadepalli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TyHil can you also sign off on this?

Copy link
Member

@TyHil TyHil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! One thing, can you add a little tidbit to the README.md about how to run this with npm run documentation. Maybe @AbhiramTadepalli would like you to give a little spiel at the next Trends meeting too.

Also just wanted to confirm if any more packages from here can be removed and if any can be moved from dependencies to devDependencies as this is only something we'll run for development.

@AbhiramTadepalli
Copy link
Contributor

@NishilJ I'm good to merge once you address these 2 things

@NishilJ
Copy link
Contributor Author

NishilJ commented Feb 22, 2025

Okay, I will add some instructions to the main page and see if any more unused dependencies can be removed. I mention the naming scheme issue, I think I will add it in this pr for ease of use. Do you have any preference for the casing that all component names, component file names, and component folder names can follow?

@TyHil
Copy link
Member

TyHil commented Feb 22, 2025

I think most have a capital letter to start for the folder, lowercase for the file, and uppercase for the default exported function in the file. That would probably reduce the number of changes most.

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.

3 participants