Light doc update #210
Closed
Light doc update #210
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
* re init my mess dates * update for consistency * moving format to intl * tests with also fr local * dico * dateDisplay update * Humm * tmp rename to format_fns * realignement & doc update * add a playground * Month & monthYear * DateField * Date Range * Month done * rmv all usage of dateDisplay * Nice nice nice * casing * enums casing * oups, need to comment fr for now in the doc * formats * okay with date of week * update docs * add changeset * rmv dateDisplay * cleanup * dico * keep Day default * rmv useless * Okay, adding DayTime & TimeOnly * of course, updating doc is always good :) * Swtich default to use Tokens enum
* Squash all theme changes into single commit * Add changeset * Enter prerelease mode and version packages * Add Kbd component. Show keyboard shortcuts on ThemeButton menu * Read themes/colors from tailwind config, including Daisy UI (with mapping). Supports generating optional colors and further extension and flexability. * Process daisy themes to generate lightThemes/darkThemes based on color-scheme value * Add changeset * Version bump to 0.58.0-next.1 * Add styles (with daisy) as top-level export * Version bump to 0.58.0-next.2 * Add commonjs and esm versions of daisy module * Version bump to 0.58.0-next.3 * Remove daisy from top-level exports * Version bump to 0.58.0-next.4 * Rename `error` / `error-content` to `danger` / `danger-content` * Fix pnpm-lock.yaml using `pnpm install` (ERR_PNPM_ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE The lockfile is broken! Resolution step will be performed to fix it.) * Add `accent` and `neutral` theme colors * Cleanup * Update some leftover `error` => `danger` color references * Extra tailwind plugin into multiple files for better readability * Use darker "-content" color for default `fill` variant (distinguish from `fill-light`) * Simplify naming and impl. of foregroundColor() and add lightenColor() (to match darkenColor()) * Register 100-900 shades for all semantic and state colors. Replace color-mix() usage (including Tailwind *-mix-* utils) with new shades * Use lib/styles/themes for types as well * Replace SvelteComponentTyped with SvelteComponent * Version bump to 0.58.0-next.5 * Cleanup * Remove unused css files * Simplify * Support changing colorSpace (rgb, hsl, or oklch) * Improve theme page preview and add menu item * Improve default border color * Fix handling of hsl() color space by clamping to RGB values (to not exceed 100% saturation or lightness). Matches rgb() color * Version bump to 0.58.0-next.6 * Use same surface-content/20% outline color as border color * Remove explicit border colors that match default (border-surface-content/20) and replace some border-surface-### with default (surface-content/20) * Version bump to 0.58.0-next.7
* Rename settings `theme` to `classes` in preparation for adding theme support * Rename getComponentTheme to getComponentClasses
* Move theme management to a store that lives in the context * changeset * Use cross-framework-compatible browser value * handle post-load changes in prefers-color-scheme * better browser stub-out
* add ThemeInit component that place script inside <head> tag * Fix bug * proper sorting * instantiate ThemeInit inside Settings component * add comment about stringified function
…n theme (ex. Skeleton provides the shades 100-900). Map `{color}-500` to `{color}` if not defined. Generate neutral color if not defined
…ust solution is available)
* refacto peer dev * @changesets/cli is only for library developers * rehype-slug is only for the `svelte-ux` doc it can go to devDep * @fortawesome/free-solid-svg-icons is only in the doc
…ttings after component initialization (#191) * move format functions onto settings object * update uses of formatting functions to fit new settings paradigm * start transferring to store-based locale settings * checkpoint * update templates, add back custom date formatting * upadte format samples * update number tests * clean up custom variant a bit, improve format function type definition * remove date and number subformatters * fixes * fix missing style * better label * allow setting locale to one not explicitly supported * fix a few old format calls * add function type possibility to column format
* fix circular reference * remove knownLocales * fix date tests * add locale exports, hide exports of a few internal-only functions * changeset
* add WeekStartsOn defaults depending on the locale * init a Language Select comp
* Rename `cssVars` action to `styleVars` and do not prefix properties with `--` by default (more flexible)
* [SelectField] Fix toggling display of options menu using toggleIcon. Ignore toggling when clicking on SelectField border. Support hiding toggleIcon (`<SelectField toggleIcon={null} />
* [SelectField] Add `stepper` prop to iterate through options (like `MenuField`)
* [MenuField] Expose `selected` option via prop (similar to `SelectField`)
* [SelectField Add stepper example
* Move `processThemeColors()` from tailwind plugin to $lib/styles/theme to allow calling at runtime (theme generator frontend). Add types
* Update skeleton.ts to match skeleton.cjs (to be removed)
* Beginning work of theme generator
* Read themes from `themes.json` file for both tailwind config and theme selector. Remove daisy/skeleton commonjs modules. Add `getThemeNames` to split based on `color-scheme`. Ultimately simplifies a lot
* Add "Copy all" daisy and skeleton options
* Use <ThemeSelect> or <ThemeSwitch> based on more than 1 light/dark theme
* Fix skeleton dark themes after refactor
* Add explicit daisy themeName list to hopefully fix build (similar to skeleton)
* Set initial theme selections (fix reactivity infinite loop)
* [SelectField] Use `selectValue(...)` instead of `value = ...` so `change` is dispatched (and other consistent updating)
* Change light/dark preview based on which input was last changed
* Support overriding doc themes wtih generator (custom) themes
* Fix setting `prefers-color-scheme: dark` override
* Use a local copy of Skeleton themes to fix Cloudflare build (work around Node.js runtime issue)
* Improve handling of `-50` shade when `-100` exists (ex. Skeleton)
* Update site dark/light mode with preview for better experience (previewing and applying)
* Support custom Ior exisitng) theme editing
* Add state colors and support showing/hiding optoinal colors
* Add "Copy all themes" menu item
* [ColorField] Support `hex` entry
* Register all themes (daisy + skeleton)
* Format files (fix lint error)
* Add changeset
* make DateField format and mask reactive to locale changes * Make Input component reactive to changes in mask
…dark, and fix width on mobile)
…r buttons (after darkening "fill")
* add fr translation & use the "week" to fit the weekstartOn * range & fr & reactivity * adding more translation * internal var name * typeHelpers * fix my typo 🙈
🦋 Changeset detectedLatest commit: dbcd18b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
No description provided.