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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-10
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
First off, thanks for taking the time to contribute! ❤️
4
4
5
-
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
5
+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
6
6
7
7
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
8
8
>
@@ -82,11 +82,11 @@ Once it's filed:
82
82
83
83
- The project team will label the issue accordingly.
84
84
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
85
-
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
85
+
- If the team can reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
86
86
87
87
### Suggesting Enhancements
88
88
89
-
This section guides you through submitting an enhancement suggestion for Selectize, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
89
+
This section guides you through submitting an enhancement suggestion for Selectize, **including entirely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your request and find related suggestions.
90
90
91
91
#### Before Submitting an Enhancement
92
92
@@ -102,7 +102,7 @@ Enhancement suggestions are tracked as [GitHub issues](https://github.com/select
102
102
- Use a **clear and descriptive title** for the issue to identify the suggestion.
103
103
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
104
104
-**Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point, you can also tell which alternatives do not work for you.
105
-
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part to which the suggestion is related. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. <!-- this should only be included if the project has a GUI -->
105
+
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part to which the suggestion is related. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. <!-- this should only be included if the project has a GUI -->
106
106
-**Explain why this enhancement would be useful** to most Selectize users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
107
107
108
108
### Your First Code Contribution
@@ -117,9 +117,9 @@ Running `make` will build the project, run all tests, and update the distributio
117
117
118
118
Running `npm start` on your repo will start a web server allowing you to view a local copy of this documentation, where you can test your changes against our example pages.
119
119
120
-
If you are adding a new plugin, you should also add a corresponding example page to the `/docs/docs/plugins` directory.
120
+
If you are adding a new plugin, you should add a corresponding example page to the `/docs/docs/plugins` directory.
121
121
122
-
You can then run the examples at `http://localhost:4000/`.
122
+
You can then run the examples at `https://loopback.website:4000/`.
123
123
124
124
### Improving The Documentation
125
125
@@ -134,7 +134,5 @@ If you're motivated to fix a bug or to develop a new feature, we'd love to see y
134
134
- Make sure tests pass: Run `npm test` to make sure your changes don't break existing functionality
135
135
- Do not make changes to files in `/dist`. Limiting your edits to files in `/src` directories keeps the size of your pull request down and makes it easier for us to evaluate. We'll update the `/dist` folder after your pull request is approved.
136
136
- Add tests: In the best-case scenario, you are also adding tests to back up your changes, but don't sweat it if you don't. We can discuss them at a later date.
137
-
- Squash your commits together in one or a few complete, logical commits,
138
-
with a concise and descriptive message. One commit means one
139
-
feature/bugfix/thing that has changed, or a diff bringing the code one
140
-
step forward to a better, working state.
137
+
- Squash your commits together in one or a few complete, logical commits with a concise and descriptive message. One commit means one
138
+
feature/bugfix/thing that has changed or a diff bringing the code one step forward to a better, working state.
Copy file name to clipboardExpand all lines: docs/docs/demos/email.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
id: email-contact
3
3
title: Custom Rendering and Validation
4
-
description: This demonstrates two main things, (1) custom item and option rendering, and (2) item creation on-the-fly. Try typing a valid and invalid email address.
4
+
description: This demonstrates two main things, (1) custom item and option rendering and (2) item creation on-the-fly. Try typing a valid and invalid email address.
@@ -12,7 +12,7 @@ Selectize is a JavaScript library that provides a rich user experience for selec
12
12
13
13
### What you'll need
14
14
15
-
Selectize requires jQuery. We also include styles for bootstrap, but also provide raw Less and Sass files for you to customize with any framework you like.
15
+
Selectize requires jQuery. We also include styles for bootstrap and provide raw Less and Sass files for you to customize with any framework you like.
16
16
17
17
If you want to use the Drag & Drop plugin, you'll need jQuery UI.
18
18
@@ -37,23 +37,20 @@ yarn add @selectize/selectize
37
37
38
38
### Install with cdn
39
39
40
-
The fastest way to add Selectize into your project is to just include the js and css from jsDelivr.
40
+
The fastest way to add Selectize to your project is to include the js and css from [cdnjs](https://cdnjs.com/libraries/selectize.js).
0 commit comments