You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [docs]: added missing installation check boxes and fixed typo
* [core]: fixed typos
* [core]: Yarn and Storybook migration (#160)
* [migration]: all packages on kit-next.377 and use storybook template
* [@svelteui/core]: configuring story book (viewport modifications and set up)
* [@svelteui/core]: moved lib contents to src
* [@svelteui/core]: fixed stories for button
* [core]: fixed all eslintrcs
* [core]: started theme setup for core package
* [core]: storybook working with dark and light theme
* [core]: revert some changes and remove logs
* [core]: remove unused logic
* [core] yarn migration (#157)
* [core]: migrate to yarn
* [docs]: update contribution guide to include yarn
* [core]: modify github pipelines to use yarn
* [core]: format and lint code
* [core]: update yarn.lock (#161)
Co-authored-by: BeeMargarida <[email protected]>
* [@svelteui/core]: support number as size in Button (#165)
* [@svelteui/core]: fix missing prop type in NumberInput
* [@svelteui/core]: use new prop approach in all components
* [@svelteui/core]: remove onMouseEnter and onMouseLeave prop and use dispatch events instead
* [@svelteui/core]: simplify prop approach in Button
* [@svelteui/core]: format code - yarn format result
* [@svelteui/core]: revert yarn format
* [@svelteui/core]: remove BrowserRender, ServerRender and Fragment component (#167)
* [core]: normalize scripts with : and udpdate readmes (#169)
* [core]: sorted package jsons
* [core]: updated docs and core dev scripts
* [@svelteui/core]: Export all components prop types (#173)
* [@svelteui/core]: export all component types instead of the whole styles
* [core]: yarn lock
* [core]: linting + format all package.json
* [@svelteui/core]: fix select autocomplete logic that showed previous option on reload (#177)
* [@svelteui/core]: fix Tabs bug where events inside tab content were not propagated due to node handling (#180)
* [@svelteui/prism]: fix indentation problem on the first line (#181)
* [@svelteui/prism]: fix indentation problem on the first line
* [core]: remove package.json from prettier
* [docs]: fix docs dev command, add docs node_modules to clean:all command and update tsconfig of core
* [@svelteui/demos]: remove unecessary code from demos code examples (#182)
* [@svelteui/core]: updated tsconfig
* [@svelteuidev/core] Menu custom control (#184)
* [@svelteui/core]: support for custom control in Menu
* [@svelteui/core]: expose menu functions for opening/closing/toggling the menu state outside the component
* [@svelteui/demos]: demo for Menu custom control
* [docs]: add custom menu control examples to docs
* [docs]: add missing period
* [core]: remove flacky test
* [@svelteui/core]: add role and aria info to custom menu control
* [@svelteui/core]: added menu story
* [core]: syncpack was failing script
* [docs]: added modal clarification and removed banner
* [core]: changed publish scripts due to unknown npm bug
* [@svelteui/core]: menu story
* [core]: fixed peerdeps versioning issues
* [release]: 0.7.2
* [core]: fixed dev:core script
* [@svelteui/composables]: migrated directory structure from the use of lib
* [@svelteui/composables]: removed storybook config
* [core]: fixed package json
* [core]: changed yarn install to yarn in workflow
* [core]: Storybook for core, composables and dates packages (#190)
* [core]: removed unused stories from packages
* [core]: moved storybook configuration to configuration folder and updated paths
* [core]: working storybook that shows core stories
* [core]: simple use-click-outside story for testing purposes
* [core]: delete old storybook folders
* [core]: stabilize storybook config
* [@svelteui/composables]: change to
* [@svelteui/dates]: change to
* [core]: stories for dates, core and composables and simple example stories
* [core]: format and lint fixes
* [@svelteui/prism]: ignore line for prettier in prism
* [@svelteui/composables]: small fix in alias
* [@svelteui/composables]: small fixes to alias
* [core]: bump vitest, cleanup dependencies, remove unecessary test setup and fix tests
* [core]: update scripts + contributing scripts
* [@svelteui/core]: Fixes#189 - fix Switch disabled style and add dark styles (#192)
* [@svelteui/core]: fix switch disabled style and add dark mode style
* [@svelteui/core]: fix switch disabled style and add dark mode style
* [core]: migrate to new svelte-package approach since svelte-kit package is deprecated (#194)
* [docs]: improve Modal target warning and demo (#197)
* [@svelteui/core]: fix type inconsistency in actions API (#198)
* [core]: move all packages outside lib folder (#196)
* [@svelteui/preprocessors]: moved code from src/lib into src
* [@svelteui/prism]: moved code from src/lib into src
* [@svelteui/tests]: moved code from src/lib into src/
* [@svelteui/demos]: moved code from src/lib into src
* [core]: removed static files from packages
* [@svelteui/dates]: moved src/lib into src/
* [core]: fix packaging with new aliases: bump svelte-package with fix
* [docs]: fix paths for components
* [@svelteui/core]: fix test setup
* [core]: fixed pub script and changed storybook to dev
* [core]: made modal error more clear
* [core]: [release] 0.7.3
* [core]: updated readme for rebase
* [@svelteui/core]: fix Tab dark mode color and simple story for testing purposes (#201)
* [@svelteui/core]: fix element retrieval in Modal (#203)
* [@svelteui/core]: fix switch disable behaviour
* [core]: bump svelte version
* [core]: update yarn lock
* [core]: do not change package.json on prettier since it changes the peerDependencies semver (#213)
* [@svelteui/core]: add Chip and ChipGroup components (#209)
* [@svelteui/core]: add Chip and ChipGroup components
Stubbed first draft of components. Not ready yet. Mostly copied from other components like Checkbox and also Mantine. Not tested.
Signed-off-by: Brian Evans <[email protected]>
* [@svelteui/core]: change Chip styles after code review
Edited the styles for Chip based on PR feedback.
Used color functions where possible, instead of hard coding.
Also changed the way variants are selected.
Added a checkmark when a chip is selected.
Signed-off-by: Brian Evans <[email protected]>
* [@svelteui/core]: added Storybook story for Chip
Signed-off-by: Brian Evans <[email protected]>
* [@sveltui/core]: make Chip label dynamic
Co-authored-by: Ana Margarida Silva <[email protected]>
* [@svelteui/core]: Chip styling and Story changes
Based on PR feedback:
- added more stories to storybook for sizing, and the different states
- fixed dark mode selectors to use old method [`${theme.dark} &`]
- made the label dynamic from label prop if no children provided to component
Signed-off-by: Brian Evans <[email protected]>
* [@svelteui/core]: hide input element in Chip
Wrap the input element in a div which hides it.
Signed-off-by: Brian Evans <[email protected]>
* [@svelteui/core]: ChipGroup storybook Stories
Added Stories for testing the ChipGroup.
Removed some defaults from the ChipGroup component since these are set in Chip.
Removed the input type prop, as it's not necessary.
Signed-off-by: Brian Evans <[email protected]>
* [@svelteui/core]: Chip disabled checked styling
Signed-off-by: Brian Evans <[email protected]>
Signed-off-by: Brian Evans <[email protected]>
Co-authored-by: Kamell <[email protected]>
Co-authored-by: Ana Margarida Silva <[email protected]>
* [docs]: fix docs paths (#214)
* [docs]: fix docs paths for svelteui-core and edit page
* [docs]: fix doc paths for composables
* [docs]: fix doc paths for dates
* [docs]: fix doc path for preprocessors
* [@svelteui/core]: Fix menu placement bug (#216)
The menu placement was not working when a custom control was used. I fixed the bug by making the custom control the reference, unless it doesn't exist, then use the default control element. The Story demonstrates the fix.
Signed-off-by: Brian Evans <[email protected]>
Signed-off-by: Brian Evans <[email protected]>
* [core]: fix storybook global undefined error
* [@svelteui/core]: fix type, TS errors and format
* [docs] README documentation for NPM package (#218)
* [docs]: Documentation for Chip and ChipGroup (#220)
* [@svelteui/core]: fix Chip export
* [@svelteui/core]: improvements to Chip and ChipGroup - support multiple or not
* [@svelteui/demos]: chip demos
* [@svelteui/core]: format fixes
* [docs]: chip docs
* [@svelteui/core]: use same path for linting command as in format
* [core]: Fix npm dependency errors on install (#222)
* [docs]: rename prepare script to not be called by husky
* [core]: fix vite npm dependency error
* [core]: add deno to contributing guide
* [core]: small fix
* [@svelteuidev/demos] Fixes#225: Gradient problem in docs (#228)
* [@svelteui/core]: badge simple story and fix in prism styles
* [docs]: add rollup to fix error on dev
* [@svelteui/demos]: fix CompositeRender event dispatch
* [@svelteui/core]: add IconRenderer (#223)
* [core]: fixes#233 - update dev docs setup documentation
* [@svelteui/core]: refactor import
* [core]: update tsconfigs
* [@svelteui/core]: make Code props optional (#238)
* [@svelteuidev/core] Fix modal target problem (#239)
* [@svelteui/core]: fix modal target check and affix props
* [@svelteui/demos]: fix modal demos
* [@svelteui/demos]: revert target=body in modal demos
* [docs]: Changed the line-height and added animations on scroll in the homepage (#240)
* [docs]: Changed lineHight of text in homepage to match Features.svelte
* [docs]: Added transitions on scroll for Features.svelte
* [docs]: Changed variable name to improve clarity
* [docs]: Ran tests and linted code
* [docs]: Changed height of wrapper div
* [docs]: fix height in docs
* [core]: update README
* [docs]: Improvements in sentences and changed styling of NextSteps component (#244)
* [docs]: Changed lineHight of text in homepage to match Features.svelte
* [docs]: Added transitions on scroll for Features.svelte
* [docs]: Changed variable name to improve clarity
* [docs]: Ran tests and linted code
* [docs]: Changed height of wrapper div
* [docs]: Improvements in sentences and styling
* [docs]: Hopefully resolved conflict
* review changes
* [@svelteui/demos] Fixed incorrect value being shown (#247)
* [core]: exclude peer deps in syncpack set-semver-ranges script (#246)
* [@svelteui/core]: fix Grid spacing prop reactivity and style (#248)
* [@svelteui/core]: exclude open/close events from event forwarding in Meny (#245)
* [@svelteuidev/composables] Fixes#241: focus trap action and usage on modal (#243)
* [@svelteui/composables]: use-focus-trap action
* [@svelteui/core]: use focus-trap action in modal
* [@svelteui/composables]: story for action focus-trap
* [docs]: focus-trap docs
* [@svelteuidev/composables] use-move action (#242)
* [@svelteui/composables]: use-move action to move an element with the mouse movement
* [@svelteui/composables]: set custom events for native DOM elements typings
* [@svelteui/composables]: use-move finished with working story
* [@svelteui/composables]: export use-move
* [@svelteui/composables]: fix namespace and story style
* [@svelteui/demos]: use-move demo
* [docs]: use-move docs
* [docs]: fix in description
* Modal story added
Signed-off-by: Brian Evans <[email protected]>
Co-authored-by: Kamell Perry <[email protected]>
Co-authored-by: Kamell <[email protected]>
Co-authored-by: Brisklemonade <[email protected]>
Co-authored-by: Jason Xu <[email protected]>
Co-authored-by: Brian Evans <[email protected]>
Co-authored-by: Kyle Shepherd <[email protected]>
Co-authored-by: Caladan <[email protected]>
Copy file name to clipboardExpand all lines: apps/docs/src/pages/basics.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ title: Learn the basics
13
13
14
14
<MinorHeading />
15
15
16
-
This guide will help you get familiar with core SvelteUI concepts. Please read this guide and the **theming** section before starting development to learn about all available theming features and component behaviors.
16
+
This guide will help you get familiar with core SvelteUI concepts. Please read this guide and the [theming](theming/svelteui-provider) section before starting development to learn about all available theming features and component behaviors.
17
17
18
18
## SvelteUI packages
19
19
@@ -40,15 +40,15 @@ To learn how to dynamically change the theme by reading the [dark theme guide](t
40
40
41
41
## Server side rendering
42
42
43
-
SvelteUI components work in SvelteKit environments without any configuration needed. However, they aren't SSR compatible by default. To setup SSR, follow the server side rendering guide below, It's really easy to set up!
43
+
SvelteUI components work in SvelteKit environments without any configuration needed. However, they aren't SSR compatible by default. To setup SSR, follow the server side rendering guide below. It's really easy to set up!
44
44
45
45
-[Server side rendering with SvelteKit](theming/ssr)
46
46
47
47
## TypeScript
48
48
49
49
### Exported types
50
50
51
-
@svelteuidev/core package export all types to help you build components and styles with TypeScript, some notable ones are:
51
+
`@svelteuidev/core` package export all types to help you build components and styles with TypeScript. Some notable ones are:
52
52
53
53
-`ColorScheme` – union of `'light' | 'dark'`.
54
54
-`SvelteUIColor` – union of all default colors.
@@ -113,7 +113,7 @@ Under normal circumstances you wouldn't be able to use actions on components bec
113
113
114
114
## Bindings
115
115
116
-
All components support binding their top-level element via the element prop instead of `this`. This allows you to get a reference to a DOM node (as a supplement to `bind:this`):
116
+
All components support binding their top-level element via the `element` prop instead of `this`. This allows you to get a reference to a DOM node (as a supplement to `bind:this`):
The `use-focus-trap` action traps the focus inside a given DOM node. The node must include at least one focusable element, and it will give priority to a node with the `autofocus` property.
With the Intersection Observer API, use-intersection gets information about the intersection of a given element with its scroll container or body element:
21
+
With the Intersection Observer API, `use-intersection` gets information about the intersection of a given element with its scroll container or body element:
22
22
23
23
<Demodemo={ComposableDemos.useIoDemo.usage} />
24
24
@@ -33,7 +33,7 @@ With the Intersection Observer API, use-intersection gets information about the
33
33
34
34
## Events
35
35
36
-
The use-clipboard action dispatches custom events. Each custom event takes a callback function just like other events.
36
+
The `use-clipboard` action dispatches custom events. Each custom event takes a callback function just like other events.
Copy file name to clipboardExpand all lines: apps/docs/src/pages/contributing.md
+33-26Lines changed: 33 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,31 +19,31 @@ title: 'Contributing'
19
19
20
20
## Ways to contribute
21
21
22
-
-**Improve documentation:**fix incomplete or missing docs, bad wording, examples or explanations
23
-
-**Give feedback:**we are constantly working on making SvelteUI better, please share how you use SvelteUI, what features are missing and what is done good via GitHub Discussions
24
-
-**Share SvelteUI:**share link to SvelteUI docs with everyone who can be interested, share SvelteUI on Twitter
25
-
-**Contribute to codebase:**propose new feature via GitHub Issues or find an [existing one](https://github.com/svelteuidev/svelteui/labels/help%20wanted) that you are interested in and work on it
26
-
-**Give us a code review:**help us identify problems with [source code](https://github.com/svelteuidev/svelteui) or make SvelteUI more performant
22
+
-**Improve documentation:**Fix incomplete or missing docs, bad wording, examples or explanations.
23
+
-**Give feedback:**We are constantly working on making SvelteUI better, please share how you use SvelteUI, what features are missing and what is done good via GitHub Discussions.
24
+
-**Share SvelteUI:**Share the link to SvelteUI docs with everyone who can be interested, share SvelteUI on Twitter.
25
+
-**Contribute to codebase:**Propose new features via GitHub Issues or find an [existing one](https://github.com/svelteuidev/svelteui/labels/help%20wanted) that you are interested in and work on it.
26
+
-**Give us a code review:**Help us identify problems with the [source code](https://github.com/svelteuidev/svelteui) or make SvelteUI more performant.
27
27
28
28
## Contributing workflow
29
29
30
-
- Decide what you want to contribute
31
-
- If you want to implement a new feature, discuss it with a maintainer ([Discord](https://discord.gg/2J2xmzCS79) or [Discussions](https://github.com/svelteuidev/svelteui/discussions/categories/feature-requests)) before jumping into code
32
-
- After finalizing the issue details and the code, please follow commit convention
33
-
- Submit a PR if everything is fine
34
-
- Get a code review and fix all issues noticed by a maintainer
35
-
- PR is merged, and we're done!
30
+
- Decide what you want to contribute.
31
+
- If you want to implement a new feature, discuss it with a maintainer ([Discord](https://discord.gg/2J2xmzCS79) or [Discussions](https://github.com/svelteuidev/svelteui/discussions/categories/feature-requests)) before jumping into code.
32
+
- After finalizing the issue details and the code, please follow commit convention.
33
+
- Submit a PR if everything is fine.
34
+
- Get a code review and fix all issues noticed by a maintainer.
35
+
-The PR is merged, and we're done!
36
36
37
37
## Commit convention
38
38
39
39
SvelteUI is a monorepo and it is important to write clear commit messages to keep the git history clean.
40
-
All commits made in this repository are divided in 3 groups:
40
+
All commits made in this repository are divided into 3 groups:
41
41
42
-
-**package commits** related to particular package
42
+
-**package commits** related to a particular package
43
43
-**docs commits** related to documentation
44
44
-**core commits** only related to repository tooling and not associated with any package
45
45
46
-
This repo uses commitizen to make commits easier. In order to commit changes made, you should run the `yarn cm` command. Once you have done that, the commitizen cli messages will guide you through the commit process. Commit message consists of 2 parts:
46
+
This repo uses commitizen to make commits easier. In order to commit the changes made, you should run the `yarn cm` command. Once you have done that, the commitizen CLI messages will guide you through the commit process. Commit message consists of 2 parts:
47
47
48
48
```bash
49
49
[type]: Message
@@ -58,7 +58,7 @@ Examples:
58
58
59
59
## Git branches
60
60
61
-
-**main** - When the project hits 1.0, this will be for the current version, and patches for current minor version (1.0.x)
61
+
-**main** - When the project hits 1.0, this will have the current version, as well as patches for the current minor version (1.0.x)
62
62
-**next-minor** - Contains next minor version (1.x.0), most likely you would want to create a PR to this branch
63
63
-**experimental** - Up to date with next minor version (1.x.0), implementing some experimental features that may or may not be added
64
64
@@ -67,7 +67,7 @@ Examples:
67
67
- Install [editorconfig](https://editorconfig.org/) extension for your editor
You won't need to pay attention to every file within the project. All of the packages follow a similar pattern, so you should always start your journey within the `src/lib` of whatever package you choose to work on.
96
101
97
102
<Demodemo={MiscDemos.contributing.tree} />
98
103
99
-
## NPM scripts
104
+
## Yarn scripts
100
105
101
-
All packages' npm scripts are located at [main package.json](https://github.com/svelteuidev/svelteui/blob/main/package.json),
102
-
individual packages have scripts, but they should not be interacted with directly. This is due to the nature of [TurboRepo](https://turborepo.org/). All scripts should be running from the root of the monorepo.
106
+
All packages' Yarn scripts are located at [main package.json](https://github.com/svelteuidev/svelteui/blob/main/package.json),
107
+
individual packages have scripts, but they should not be interacted with directly. This is due to the nature of [TurboRepo](https://turborepo.org/). All scripts should be run from the root of the monorepo.
103
108
109
+
-`dev:docs` - runs the development environment for the docs
110
+
-`dev` - runs Storybook for all the packages that contain stories
104
111
-`clean` - removes all unnecessary files and folders from packages (i.e. node_modules)
105
112
-`format` - runs prettier on packages folder
106
-
-`lint` - runs ESLint on packages folder (run format before running lint)
113
+
-`lint` - runs eslint on packages folder (run format before running lint)
107
114
-`test` - runs tests with [vitest](https://vitest.dev/)
108
115
-`package` - generates built versions of packages (needed for cross package development)
109
-
-`repo:prepush` - runs sort, format, lint and test (run this before pushing your code)
116
+
-`prepush:repo` - runs sort, format, lint and test (run this before pushing your code)
110
117
-`cm` - runs git commands to add and commit through commitizen (this is the recommended way to commit as it follows the convention automatically)
0 commit comments