So you want to help us. Neat, you are awesome!
You can:
- Spread the word about this library or the plugin it is based on. Seriously, by just mentioning us to a friend you're already making a good difference.
- Report an issue here. It could be anything; a bug, suggestion, enhancement and even a site where you used this plugin.
- Make a pull request. This is the preferred method, because then the maintainers don't need to touch the code
See details on each of one below.
If you're just making a suggestion or pointing out something simple, don't be shy; speak in any way you can.
But in the case of a bug report, things start to get more serious.
When reporting a bug, please try to reproduce it using Gist or
jsFiddle as a template. Environment can be different and some may be fine,
some may be not. Please make sure you can clearly demonstrate the bug unless
the bug is super easy to spot like a < b
should be a <= b
.
When reproducing a bug, it's important that CSS matches the page where you encounter the bug, it could be crucial that container's and innertag's styles have to be exactly the same.
Please also provide enough information about your system and browser, if necessary, here is a template:
TextFill version:
jQuery version:
Font family:
OS/Version:
Browser/Version:
Since version 0.3.1 there is a debugging option, it can be enabled by using
debug: true
on the options. You could totally include those messages.
You have JavaScript skills and don't want to wait for us to make the changes. Great!
But take care to not:
- Update version number.
- Generate minified file.
These tasks are for releasing, contributors should not take on them.
Also, before you submit, make sure:
- The Coding style generally matches
- Have a clear description of what problem you are trying to solve with your code. If a related issue exists, just reference that instead.
- It passes all (or most) tests (open
unit-tests/tests.html
in your browser). - Optional If you're adding a new feature, we'd prefer if you could add new unit tests!
- Optional Update
README
if necessary - Optional Update
CHANGES
if worth mentioning (Add to the Development section, don't create a new release)