restore composer.json, add mysqli extension

public/vendor/editor/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Summernote's Contributor Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at summernoteis@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

public/vendor/editor/.github/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+## 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
+
+```
+At this point, you should now have a `dist/` directory populated with everything you need to use summernote.
+
+## Start local server for developing summernote.
+run local server with webpack-dev-server and watch.
+```bash
+npm run dev
+# 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 `browsers` properties in `karma.conf.js`.
+
+```
+karma: {
+  all: {
+    browsers: ['PhantomJS'],
+    reporters: ['progress']
+  }
+}
+
+```
+
+Or, pass `--browsers` argument via `npm run test` command.
+```
+$ npm run test -- --browsers Safari,Firefox
+```
+
+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.
+
+## Test a part of test
+
+If you would like to run some part of your test codes, use the watch mode.
+
+```bash
+$ npm run test:watch
+```
+
+`karma` will run test and keep waiting other test requests. And then, run `test:grep` in another terminal. Below shows how to run `LinkDialog` related tests only.
+
+```bash
+$ npm run test:grep LinkDialog
+```
+
+## 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.
+1. A body container also has inline nodes sometimes. This inline nodes will be wrapped with `<p>` when enter key pressed.
+1. A block node only has inline nodes.
+1. A inline nodes has another inline nodes
+1. `#text` and void inline node doesn't have children.

public/vendor/editor/.github/FUNDING.yml

@@ -0,0 +1,8 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+custom: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S8F8AAD3YSD6Q&source=url

public/vendor/editor/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,29 @@
+Before submitting an issue, please make sure to search for already open issues, and add to that. This way we can track issues more easily. Thank you, and Thanks for using Summernote.
+
+Please answer the below questions, this will help us to more easily resolve whatever issues you are having, and direct issue to the suitable people to with your issue or to give you correct answers.
+
+#### Description of your Issue or Request:
+Please provide a short description of the issue or request. If you don't provide one, we can't expedite helping to fix your issue or fullfill your request.
+
+#### steps to reproduce (Add more if necessary):
+1.
+
+2.
+
+3.
+
+
+#### What is your Operating System, Browser and Version and Summernote Version you are using:
+This can help find and resolve any issues.
+1. Operating System:
+
+2. Browser and Version:
+
+3. Summernote Version (including which BS3, BS4, Lite or All):
+
+
+#### screenshot of issue
+Add screenshot which shows your issue(if needed).
+You can make [gif from Recordit](http://www.recordit.co/).
+
+If you can make the issue using jsfiddle(https://jsfiddle.net/), We can save time to reproduce the problem.

public/vendor/editor/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+Thank you for taking the time to help us improve Summernote.
+Please be sure that you are not submitting changes made to the files in the `dist/` folder, and only to the files contained in the `src/` folder.
+
+#### What does this PR do?
+
+- awesome stuff
+- really cool feature
+- refactor X
+
+#### Where should the reviewer start?
+
+- start on the src/summernote.js
+
+#### How should this be manually tested?
+
+- click here and here
+
+#### Any background context you want to provide?
+
+- the gem needed to be updated...
+
+#### What are the relevant tickets?
+
+
+#### Screenshot (if for frontend)
+
+
+### Checklist
+- [ ] added relevant tests
+- [ ] didn't break anything
+- [ ] ...