🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP →
Sign In

react-crisp

Package Overview
Dependencies
Maintainers
2
Versions
5
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-crisp - npm Package Compare versions

Comparing version
0.1.0
 to
0.1.1
+20
.github/workflows/npm-publish.yml
# This package will publish the package on NPM
name: Publish Package
on:
release:
types: [released]
jobs:
publish-npm:
needs: eslint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v1
with:
node-version: 14
registry-url: https://registry.npmjs.org/
- run: yarn publish
env:
NODE_AUTH_TOKEN: ${{secrets.npm_token}}
+24
.github/workflows/package-ci.yml
# This workflow will run eslint for the package
name: Package CI
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
lintSrc:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [10.x, 12.x, 14.x]
steps:
- uses: actions/checkout@v2
- name: use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
- run: yarn install
- run: yarn run eslint
+76
CODE_OF_CONDUCT.md
# 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, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, 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 [opensource@mergify.io](opensource@mergify.io).
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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
+187
CONTRIBUTING.md
# Contributing to react-crisp
First off, thanks for taking the time to contribute!
The following is a set of guidelines for contributing to react-crisp.
These are mostly guidelines, not rules. Use your best judgment, and feel free
to propose changes to this document in a pull request.
## Code of Conduct
This project and everyone participating in it is governed by the
[react-crisp Code of Conduct](CODE_OF_CONDUCT.md). By participating, you
are expected to uphold this code. Please report unacceptable behavior to
[opensource@mergify.io](mailto:opensource@mergify.io).
## How Can I Contribute?
### Reporting Bugs
This section guides you through submitting a bug report for react-crisp.
Following these guidelines helps maintainers and the community
understand your report, reproduce the behavior, and find related reports.
Before creating bug reports, please perform a [cursory
search](https://github.com/Mergifyio/react-crisp/issues?q=is%3Aissue%20is%3Aopen%20)
to see if the problem has already been reported. If it has and the issue is
still open, add a comment to the existing issue instead of opening a new one.
When you are creating a bug report, please [include as many details as
possbile](#how-do-i-submit-a-good-bug-report).
> **Note:** If you find a **Closed** issue that seems like it is the same thing
> that you're experiencing, open a new issue and include a link to the original
> issue in the body of your new one.
#### How Do I Submit A (Good) Bug Report?
Bugs are tracked as [GitHub
issues](https://guides.github.com/features/issues/).
Explain the problem and include additional details to help maintainers
reproduce the problem:
* **Use a clear and descriptive title** for the issue to identify the problem.
* **Describe the exact steps which reproduce the problem** in as many details
as possible. For example, start by explaining how you use the
react-crisp package, e.g. which code you write and the error you get.
When listing steps, **don't just say what you did, but explain how you did it**.
* **Provide specific examples to demonstrate the steps**. Include links to
files or GitHub projects, or copy/pasteable snippets, which you use in those
examples. If you're providing snippets in the issue, use [Markdown code
blocks](https://help.github.com/articles/markdown-basics/#multiple-lines).
* **Describe the behavior you observed after following the steps** and point
out what exactly is the problem with that behavior.
* **Explain which behavior you expected to see instead and why.**
Provide more context by answering these questions:
* **Did the problem start happening recently** (e.g. after updating to a new
version of react-crisp) or was this always a problem?
* If the problem started happening recently, **can you reproduce the problem in
an older version of react-crisp?** What's the most recent version in
which the problem doesn't happen? You can install older versions of
react-crisp from [the npm registery](https://www.npmjs.com/package/react-crisp).
* **Can you reliably reproduce the issue?** If not, provide details about how
often the problem happens and under which conditions it normally happens.
Include details about your configuration and environment:
* **Which version of react-crisp are you using?** You can get the exact
version by running `yarn list | grep "react-crisp"` in your terminal.
* **What's the name and version of the OS you're using**?
* **What's the version of React you're using**?
### Suggesting Enhancements
This section guides you through submitting an enhancement suggestion for
react-crisp, including completely new features and minor improvements to
existing functionality. Following these guidelines helps maintainers and the
community understand your suggestion and find related suggestions.
When you are creating an enhancement suggestion, please [include as many
details as possible](#how-do-i-submit-a-good-enhancement-suggestion) and
including the steps that you imagine you would take if the feature you're
requesting existed.
#### How Do I Submit A (Good) Enhancement Suggestion?
Enhancement suggestions are tracked as [GitHub
issues](https://guides.github.com/features/issues/).
Provide the following information:
* **Use a clear and descriptive title** for the issue to identify the
suggestion.
* **Provide a step-by-step description of the suggested enhancement** in as
many details as possible.
* **Provide specific examples to demonstrate the steps**. Include
copy/pasteable snippets which you use in those examples, as [Markdown code
blocks](https://help.github.com/articles/markdown-basics/#multiple-lines).
* **Describe the current behavior** and **explain which behavior you expected
to see instead** and why.
* **Include screenshots and animated GIFs** which help you demonstrate the
steps or point out the part of react-crisp which the suggestion is
related to. You can use [this tool](https://www.cockos.com/licecap/) to
record GIFs on macOS and Windows, and [this
tool](https://github.com/colinkeenan/silentcast) or [this
tool](https://github.com/GNOME/byzanz) on Linux.
* **Explain why this enhancement would be useful** to most react-crisp
users.
* **List some other tools or applications where this enhancement exists.**
* **Specify which version of react-crisp you're using.** You can get the
exact version by running `yarn list| grep "react-crisp"` in your
terminal.
* **Specify the name and version of the OS you're using.**
* **Specify the version of React you're using**
## Code Contribution
### Hacking on react-crisp
If you're hitting a bug in react-crisp or just want to experiment with
adding a feature, follow these steps.
#### Prerequisites
- React >= 16.0
#### Cloning
``` command-line
$ git clone https://github.com/Mergifyio/react-crisp
```
#### Setup your environment
From there, you can navigate into the directory where you've cloned the
react-crisp source code and install all the required dependencies:
``` command-line
$ cd react-crisp
$ yarn install
```
#### Make your changes
``` command-line
$ git checkout -b somefeature
<edit files>
$ git commit -am 'I did some changes'
$ git pull-request
Forked repository: https://github.com/Mergifyio/react-crisp
Force-pushing branch `somefeature' to remote `github'
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 562 bytes | 0 bytes/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
To https://github.com/Mergifyio/react-crisp.git
+ 73a733f7...1be2bf29 somefeature -> somefeature (forced update)
Pull-request created: https://github.com/react-crispxyz/react-crisp/pull/42
```
### Pull Requests
* Squash your commits.
* Include examples, outputs, etc... whenever possible.
* Include screenshots and animated GIFs in your pull request whenever possible.
+201
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2020 Mergifyio
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
+10
-21
.mergify.yml

@@ -6,17 +6,10 @@ pull_request_rules:

- "#approved-reviews-by>=1"
- label!=work-in-progress
- label!=manual merge
- "check-success=lintSrc (10.x)"
- "check-success=lintSrc (12.x)"
- "check-success=lintSrc (14.x)"
actions:
merge:
strict: "smart"
method: rebase
- name: automatic merge from dependabot
conditions:
- author=dependabot[bot]
- label!=work-in-progress
- label!=manual merge
actions:
merge:
strict: "smart"
method: rebase
method: squash
- name: warn on conflicts

@@ -40,3 +33,3 @@ conditions:

conditions:
- author!=@devs
- author!=@react-crisp
actions:

@@ -46,3 +39,3 @@ dismiss_reviews: {}

conditions:
- author=@devs
- author=@react-crisp
actions:

@@ -54,3 +47,2 @@ dismiss_reviews:

conditions:
- -author=dependabot[bot]
- label!=work-in-progress

@@ -62,11 +54,8 @@ - label!=no-review-needed

- "#changes-requested-reviews-by=0"
- "check-success=lintSrc (10.x)"
- "check-success=lintSrc (12.x)"
- "check-success=lintSrc (14.x)"
actions:
request_reviews:
teams:
- devs
- name: auto add wip
conditions:
- title~=^(wip|WIP).*
actions:
label:
add: ["work-in-progress"]
- react-crisp
+13
-9
package.json
{
"name": "react-crisp",
"version": "0.1.0",
"version": "0.1.1",
"license": "Apache-2.0",
"description": "React component implementation of Crisp the messaging app",
"homepage": "https://github.com/Mergifyio/react-crisp",
"main": "./src/Crisp.jsx",
"keywords": [

@@ -15,5 +17,2 @@ "React",

},
"scripts": {
"build": "webpack"
},
"eslintConfig": {

@@ -24,3 +23,5 @@ "env": {

"extends": [
"airbnb"
"airbnb",
"plugin:import/errors",
"plugin:import/warnings"
]

@@ -40,6 +41,6 @@ },

},
"peerDependencies": {
"prop-types": "^15.7.2",
"react": "^17.0.1",
"react-dom": "^17.0.1"
"dependencies": {
"prop-types": "^15.0.0",
"react": "^16.0.0",
"react-dom": "^16.0.0"
},

@@ -56,3 +57,6 @@ "devDependencies": {

"eslint-plugin-react-hooks": "^4.2.0"
},
"scripts": {
"eslint": "eslint --ext .js --ext .jsx ./src"
}
}
+2
-2
src/Crisp.jsx

@@ -24,3 +24,3 @@ import PropTypes from 'prop-types';

this.setAttributes();
this.safeMode();
this.setSafeMode();
insertScript();

@@ -65,3 +65,3 @@ }

return (
<></>
''
);

@@ -68,0 +68,0 @@ }