bump version, add contribution to readme

Author: simeydotme

README.md

@@ -53,4 +53,17 @@ prop | type | default | description
 **handleFormatter** | `Function` | `formatter` | A function to re-format values on the handle/float before they are displayed. Defaults to the same function given to the `formatter` property
 **springValues** | `Object` | `{ stiffness: 0.15, damping: 0.4 }` | Svelte spring physics object to change the behaviour of the handle when moving
 
-**[🔗 _For full documentation and examples, see the Github Pages_](https://simeydotme.github.io/svelte-range-slider-pips/)**
+**[🔗 _For full documentation and examples, see the Github Pages_](https://simeydotme.github.io/svelte-range-slider-pips/)**
+
+
+## contribue
+
+I am very happy to accept;
+- suggestions/requests for new features or changes with examples of how they would be useful
+- pull-requests for bug fixes, or issue resolution
+- help with creating a proper test-suite
+
+When making changes/edits to the code you should use the `/test/` folder and check the Readme.md in there
+to help with testing all the functionality. I don't have real tests set up, and would appreciate anyone's 
+help who knows how to accomplish that.
+

package.json

@@ -37,7 +37,7 @@
     "src",
     "dist"
   ],
-  "version": "1.2.2",
+  "version": "1.3.0",
   "description": "Multi-Thumb, Accessible, Beautiful Range Slider with Pips",
   "repository": "https://github.com/simeydotme/svelte-range-slider-pips",
   "homepage": "https://simeydotme.github.io/svelte-range-slider-pips/",

test/README.md

@@ -7,4 +7,9 @@ Test folder for trying out combinations of options while editing the plugin.
   cd test/
   yarn install
   yarn run dev
-```
+```
+
+It's basic for now with just a large list of different sliders with different options to help identify anythingh broken.
+
+If anyone has experience with how to do actual testing for UI components and wants to start
+this off in the right direction, please get in touch using the issues feature!