.-.-.-.-.-

home/emeraadmin/public_html/node_modules/summernote/CONTRIBUTING.md000064400000004025151677306470021225 0ustar00## Contributing
* Pull requests are welcome
* Please `don't include dist/* files` on your commits.

## Coding convention
* eslint: https://eslint.org
* eslint rule: https://github.com/summernote/summernote/blob/master/.eslintrc

## Build summernote
```bash
npm install

# build full version of summernote: dist/summernote.js
npm run build

# generate minified copy: dist/summernote.min.js, dist/summernote.css
npm run dist
```
At this point, you should now have a `build/` directory populated with everything you need to use summernote.

## Start local server for developing summernote.
run local server with connect and watch.
```bash
npm run start
# Open a browser on http://localhost:3000.
# If you change source code, automatically reload your page.
```

## Test summernote
run tests with Karma and PhantomJS
```bash
npm run test
```
If you want run tests on other browser,
change the values for `broswers` properties in `karma.conf.js`.

```
karma: {
  all: {
    browsers: ['PhantomJS'],
    reporters: ['progress']
  }
}

```
You can use `Chrome`, `ChromeCanary`, `Firefox`, `Opera`, `Safari`, `PhantomJS` and `IE` beside `PhantomJS`.
Once you run `npm test`, it will watch all javascript file. Therefore karma run tests every time you change code.

## Prepush Hooks
As part of this repo, we use the NPM package husky to implement git hooks. We leverage the prepush hook to prevent bad commits.

## Document structure

```
 - body container: <div class="note-editable">, <td>, <blockquote>, <ul>
 - block node: <div>, <p>, <li>, <h1>, <table>
 - void block node: <hr>
 - inline node: <span>, <b>, <font>, <a>, ...
 - void inline node: <img>
 - text node: #text
```

1. A body container has block node, but `<ul>` has only `<li>` nodes.
2. A body container also has inline nodes sometimes. This inline nodes will be wrapped with `<p>` when enter key pressed.
4. A block node only has inline nodes.
5. A inline nodes has another inline nodes
6. `#text` and void inline node doesn't have children.
home/emeraadmin/public_html/node_modules/react-dnd-scrollzone-patch-react-17/CONTRIBUTING.md000064400000000611151677310730025465 0ustar00# Contributing

## PRs and Contributions
 * Tests must pass.
 * Follow existing coding style.
 * If you fix a bug or add a feature, add a test.

## Issues
Things that will help get your question issue looked at:
 * Full and runnable JS code.
 * Clear description of the problem or unexpected behavior.
 * Clear description of the expected result.
 * Steps you have taken to debug it yourself.
home/emeraadmin/public_html/node_modules/jquery.flot.tooltip/CONTRIBUTING.md000064400000001524151677330030022770 0ustar00## For developers/contributors

If you wish to contribute, please do so by editing the jquery.flot.tooltip.source.js file.  The other .js files are built with Grunt and should not be directly edited.

When working with external plugin support, you can use the array plotPlugins (via this.plotPlugins), which is a collection of the names of the currently loaded Flot plugins.  For instance if checking for the existance of the official
symbol plugin, you would check `if ($.inArray('symbol', this.plotPlugins) !== -1)`.

There exists a Gruntfile.js for development purposes, but please do not commit built production or minified .js files when making a pull request.  Additionally, do not change the version, because the new version could vary depending on
when the pull request is merged and how many other changes were made at the same time.
home/emeraadmin/public_html/node_modules/flot-charts/CONTRIBUTING.md000064400000006414151701372130021241 0ustar00## Contributing to Flot ##

We welcome all contributions, but following these guidelines results in less
work for us, and a faster and better response.

### Issues ###

Issues are not a way to ask general questions about Flot. If you see unexpected
behavior but are not 100% certain that it is a bug, please try posting to the
[forum](http://groups.google.com/group/flot-graphs) first, and confirm that
what you see is really a Flot problem before creating a new issue for it.  When
reporting a bug, please include a working demonstration of the problem, if
possible, or at least a clear description of the options you're using and the
environment (browser and version, jQuery version, other libraries) that you're
running under.

If you have suggestions for new features, or changes to existing ones, we'd
love to hear them! Please submit each suggestion as a separate new issue.

If you would like to work on an existing issue, please make sure it is not
already assigned to someone else. If an issue is assigned to someone, that
person has already started working on it. So, pick unassigned issues to prevent
duplicated effort.

### Pull Requests ###

To make merging as easy as possible, please keep these rules in mind:

1. Submit new features or architectural changes to the *&lt;version&gt;-work*
    branch for the next major release.  Submit bug fixes to the master branch.

2. Divide larger changes into a series of small, logical commits with
    descriptive messages.

3. Rebase, if necessary, before submitting your pull request, to reduce the
    work we need to do to merge it.

4. Format your code according to the style guidelines below.

### Flot Style Guidelines ###

Flot follows the [jQuery Core Style Guidelines](http://docs.jquery.com/JQuery_Core_Style_Guidelines),
with the following updates and exceptions:

#### Spacing ####

Use four-space indents, no tabs.  Do not add horizontal space around parameter
lists, loop definitions, or array/object indices. For example:

```js
    for ( var i = 0; i < data.length; i++ ) {  // This block is wrong!
        if ( data[ i ] > 1 ) {
            data[ i ] = 2;
        }
    }

for (var i = 0; i < data.length; i++) {  // This block is correct!
        if (data[i] > 1) {
            data[i] = 2;
        }
    }
```

#### Comments ####

Use [jsDoc](http://usejsdoc.org) comments for all file and function headers.
Use // for all inline and block comments, regardless of length.

All // comment blocks should have an empty line above *and* below them. For
example:

```js
    var a = 5;

// We're going to loop here
    // TODO: Make this loop faster, better, stronger!

for (var x = 0; x < 10; x++) {}
```

#### Wrapping ####

Block comments should be wrapped at 80 characters.

Code should attempt to wrap at 80 characters, but may run longer if wrapping
would hurt readability more than having to scroll horizontally.  This is a
judgement call made on a situational basis.

Statements containing complex logic should not be wrapped arbitrarily if they
do not exceed 80 characters. For example:

```js
    if (a == 1 &&    // This block is wrong!
        b == 2 &&
        c == 3) {}

if (a == 1 && b == 2 && c == 3) {}  // This block is correct!
```

/home/emeraadmin/www/node_modules/liftup/../../4d695/CONTRIBUTING.md.tar