Renderer.tsx updated : eventComponentName updated

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant 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 [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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/

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing
+
+We want to make contributing to this project as easy and transparent as possible and we are grateful for, any contributions made by the community. By contributing to React Pluggable, you agree to abide by the [code of conduct](https://github.com/GeekyAnts/react-pluggable/blob/master/CODE_OF_CONDUCT.md).
+
+## Reporting Issues and Asking Questions
+
+Before opening an issue, please search the [issue tracker](https://github.com/GeekyAnts/react-pluggable/issues) to make sure your issue hasn't already been reported.
+
+### Bugs and Improvements
+
+We use the issue tracker to keep track of bugs and improvements to React Pluggable itself, its examples, and the documentation. We encourage you to open issues to discuss improvements, architecture, theory, internal implementation, etc. If a topic has been discussed before, we will ask you to join the previous discussion.
+
+## Development
+
+Visit the [issue tracker](https://github.com/GeekyAnts/react-pluggable/issues) to find a list of open issues that need attention.
+
+Fork, then clone the repo:
+
+```sh
+git clone https://github.com/GeekyAnts/react-pluggable.git
+```
+
+### Building
+
+#### Building React Pluggable
+
+```sh
+yarn build
+```
+
+### Testing and Linting
+
+To only run linting:
+
+```sh
+yarn lint
+```
+
+To only run tests:
+
+```sh
+yarn test
+```
+
+### Docs
+
+Improvements to the documentation are always welcome. You can find them in the on [`syncstate.github.io`](https://github.com/react-pluggable/react-pluggable.github.io) repository. We use [Docusaurus](https://docusaurus.io/) to build our documentation website. The website is published automatically whenever the `master` branch is updated.
+
+### Examples
+
+React Pluggabel comes with a Todo App example to demonstrate various concepts and best practices.
+
+When adding a new example, please adhere to the style and format of the existing examples, and try to reuse as much code as possible.
+
+#### Testing the Examples
+
+To test the official React Pluggabel examples, run the following:
+
+Install dependencies using yarn
+
+```sh
+yarn
+```
+
+Then run the example using
+
+```sh
+yarn start
+```
+
+Not all examples have tests. If you see an example project without tests, you are very welcome to add them in a way consistent with the examples that have tests.
+
+Please visit the [Examples page](https://react-pluggable.github.io/docs/hello-world-example) for information on running individual examples.
+
+### Sending a Pull Request
+
+For non-trivial changes, please open an issue with a proposal for a new feature or refactoring before starting on the work. We don't want you to waste your efforts on a pull request that we won't want to accept.
+
+In general, the contribution workflow looks like this:
+
+- Open a new issue in the [Issue tracker](https://github.com/GeekyAnts/react-pluggable/issues)
+- Fork the repo.
+- Create a new feature branch based off the `master` branch.
+- Make sure all tests pass and there are no linting errors.
+- Submit a pull request, referencing any issues it addresses.
+
+Please try to keep your pull request focused in scope and avoid including unrelated commits.
+
+After you have submitted your pull request, we'll try to get back to you as soon as possible. We may suggest some changes or improvements.
+
+Thank you for contributing!