Conversation
…ments - Add non-Svelte base and Svelte subclass for event state - Provide createIdbqlEvent() / getIdbqlEvent() lazy factory and proxy idbqlEvent - Replace direct instance usage with getIdbqlEvent() in state and collection modules - Tests updated and run successfully
- root@0.0.25-next.0
- root@0.0.26-next.0
- root@0.0.27-next.0
- root@0.0.28-next.0
- root@0.0.29-next.0
… add skill creation guide
- root@0.0.30-next.0
- root@0.0.31-next.0
…or Tailwind v4 - Created dark-mode.md with strategies for media query, class-based, and attribute-based dark mode. - Added setup.md for Tailwind v4 installation and configuration with Vite. - Introduced theming.md detailing theming and design tokens, including @theme directive modes and OKLCH color system. - Added mcp.json for VSCode configuration to support Svelte and shadcn-svelte. - Documented migration steps and considerations in MIGRATION.md for transitioning to Svelte 5 and shadcn-svelte design system.
… CSS v4 setup instructions
- root@0.0.32-next.0
…ate pnpm-lock.yaml to remove obsolete unocss packages
…rts and structure for consistency
…ferences in migration files
…guidelines; remove AGENTS.md
…ructions - Completed migration of SCSS files to CSS in specified directories. - Added detailed instructions for snippet migration, including directory structure and component creation rules. - Updated Alert component structure and added new snippet components for Alert, TitleBar, and ToggleBar. - Introduced new CSS files for UI components like chromeFrame, boot-menu, and taskbar. - Enhanced existing components with new slots and improved structure for better maintainability. - Added TypeScript definitions for slotui components to improve type safety and developer experience.
- Updated button component imports to use new buttonIcon and buttonAction structures. - Created new snippet components for AutoComplete, Button, and others to standardize usage. - Implemented migration script to automate snippet detection and generation. - Enhanced documentation for snippet migration instructions. - Added new styles for buttonAction and buttonMenu components. - Removed deprecated button exports and organized component structure for clarity.
…proved modularity
- Updated component annotations to use the format: `<!-- @component snippet component [ComponentName] — [Description] -->` for consistency across various components. - Added new snippet components for `MenuItem`, `ConfirmInitial`, `RatingScoredIcon`, `SwitchLabel`, `InputFirst`, `InputLast`, `DataListFooter`, `GroupTitleSlot`, `LoaderEmpty`, `LoaderError`, `LoaderLoading`, `LoaderMessage`, `LoaderSuccess`, `DrawerContent`, `DrawerFooter`, `DrawerIcon`, `DrawerPrimary`, `DrawerSecondary`, `DrawerTitle`, `DrawerTop`, `LoginAvatar`, `LoginAvatarRoot`, `LoginForm`, `SlotRetrievePassword`, `PreviewZoom`, `TaskBarLeft`, `TaskBarRight`, `Child`, and various other UI components. - Ensured all new components follow the snippet structure for rendering children.
- Changed demo imports from Demoer.svelte to DemoerContent.svelte in various demo files for consistency. - Updated the export structure in index.ts files for components like ButtonAction, ButtonMenu, Confirm, and others to include additional related components. - Renamed and reorganized several components to improve clarity and maintainability.
… COMPONENT_MAP.md generation
- Converted multiple Svelte components to use TypeScript for props definition, enhancing type safety and clarity. - Updated components in the alert, autocomplete, button, confirm, rating, switch, textfield, data list, loader, navigation, login, marquee, panel, preview, taskbar, toggle bar, tool bar, window, looper, and slotted directories. - Each component now exports a specific props type using `Record<string, any>` for flexibility.
…rity and completeness
…liases - Updated export structure in various component index files to use named exports instead of object exports, allowing for more flexible imports. - Added aliases for components to maintain backward compatibility with previous export styles. - Removed unnecessary comments and improved code readability. - Introduced a new theme.css file for theming support and integrated it into the main layout. - Enhanced slotui-mixins.css with additional utility classes and improved organization.
…e components for consistency - Changed 'pad-*' to 'p-*' in Finder.svelte, Jsoner.svelte, Drawer.demo.svelte, Tabs.demo.svelte, BootStrApp.svelte, Explorer.svelte, Header.svelte, Login.demo.svelte, Login.svelte, MenuList.demo.svelte, Panel.demo.svelte, Popper.demo.svelte, ToolBar.demo.svelte, Window.demo.svelte, Looper.svelte, and various routes. - Updated tailwind.config.js to extend theme colors and box shadows. - Updated pnpm-lock.yaml to include new tailwindcss plugins and updated dependencies.
- Updated layout classes from "flex-v" to "flex flex-col" in various demo files to standardize vertical alignment. - Adjusted gap sizes in multiple components for better spacing consistency. - Renamed several exports in index files for clarity and brevity. - Enhanced the structure of demo pages to ensure uniformity in presentation. - Made minor adjustments to component citations and descriptions for clarity.
…ith detailed checks for Svelte components
…lte 5 and Tailwind CSS - Updated MIGRATION.md to clarify project status and migration steps. - Added detailed tracking for component adaptation and integration with shadcn-svelte. - Enhanced check-internal-typs.js script to include style checks for postcss usage, tailwindcss reference, and external CSS imports. - Improved reporting in COMPONENT_MAP.md to reflect new style-related checks and compliance metrics.
- Updated all Svelte components to change the style language from SCSS or CSS to PostCSS. - Ensured that global styles are imported correctly with the new syntax. - This change enhances consistency across the codebase and prepares for future style enhancements.
…s files - Added `@reference "tailwindcss"` to various Svelte components to ensure Tailwind CSS is utilized. - Updated the `make-component-maps.js` script to clarify the removal of external CSS imports. - Created new `types.ts` files in multiple components to support type definitions.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.