-
Notifications
You must be signed in to change notification settings - Fork 0
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
Format configuration files and add Storybook support #35
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…prove .prettierrc configuration for JSON and YAML files with a tab width of 2 style: format various configuration files for consistency and readability style(tsconfig.json, .eslintrc.json): format JSON files for improved readability and maintainability, and add ignore pattern for storybook-static in .eslintrc.json feat(client): initialize Storybook configuration and add package.json for client app chore(client): create preview.ts file for Storybook and update project.json formatting for consistency chore(client): format tsconfig.json and tsconfig.spec.json for improved readability and maintainability feat(client): add support for storybook configuration in tsconfig.json to enhance development experience with stories feat(client): add tsconfig for Storybook to support TypeScript stories and configuration style(server-e2e): format .eslintrc.json and project.json for improved readability and consistency style(tsconfig, eslint): format JSON files for consistent indentation and readability style(package.json, project.json, tsconfig.app.json): format JSON files for consistent indentation and readability style(tsconfig, eslint): format JSON files for consistent indentation and readability style(graph): format package.json and project.json for consistent indentation and readability style(tsconfig): format JSON files for consistent indentation and readability across graph library configuration files feat(nx.json): add Storybook configuration and exclude related files from build feat(package.json): add Storybook dependencies to support UI component development and testing style: format .eslintrc.json and package.json for consistent indentation and readability style(project.json, tsconfig.json): format JSON files for consistent indentation and readability style(plugins): format JSON configuration files for improved readability and consistency style(openai): format package.json and project.json for consistent indentation and readability style(tsconfig): format JSON files for consistent indentation and readability across tsconfig configurations
…intain empty directories for components, decorators, and pages
…nt theming refactor(global.css): simplify Mantine CSS import path for better readability refactor(layout.tsx): replace MantineProvider with AppProvider for improved structure feat(AppProvider): create AppProvider component to encapsulate MantineProvider chore(cleanup): remove unused decorators and pages directories from stories feat(stories): add Storybook stories for the App page component to enhance UI testing and documentation chore(package.json): reorganize scripts for better clarity and add Storybook script for client development
…r consistent context fix(storybook): update stories path in main.ts to include all .stories.tsx files refactor(page): reorganize component imports to reflect new directory structure feat(stories): create page.stories.tsx for Home page to facilitate Storybook integration fix(tests): update import path for mantineTheme in index.spec.tsx to match new structure feat(AppProvider): update import path for mantineTheme to improve structure feat(ColorSchemeToggle): add ColorSchemeToggle component for theme switching feat(Faq): create Faq component with styles and stories for better documentation and testing feat(Faq): add FAQ component to provide users with answers to common questions feat(Features.module.css): create styles for FAQ component and other UI elements to enhance user experience feat(Features): add Features component and its Storybook stories to showcase key functionalities and improve documentation feat(footer): add Footer component with social media links and styles for better user engagement feat(footer): create Footer stories for Storybook to facilitate component testing and documentation feat(Header): add Header component with styles and Storybook integration for better UI representation and testing feat(Hero): add Hero component styles and Storybook configuration to enhance UI and documentation feat(client): add Hero component for showcasing AIGraphr features and create mantine theme configuration chore(client): remove empty .gitkeep file from components stories directory
…ppProvider component to enhance structure and theming capabilities in the application
… path for consistency across configurations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes various commits that format configuration files for consistency and readability. It also adds support for Storybook configuration in the client app, including the initialization of Storybook configuration files and the addition of necessary dependencies. These changes enhance the development experience with stories and improve UI component testing and documentation.