diff --git a/.github/ISSUE_TEMPLATE/workflows/Zapier.yml b/.github/ISSUE_TEMPLATE/workflows/Zapier.yml deleted file mode 100644 index 3665dd58..00000000 --- a/.github/ISSUE_TEMPLATE/workflows/Zapier.yml +++ /dev/null @@ -1,34 +0,0 @@ -# This is an action to close asana tasks that were generated by Github issues - -name: Zapier web hook - -# Controls when the workflow will run -on: - # Triggers the workflow on push or pull request events but only for the "main" branch - issues: - types: [closed] - -permissions: - issues: read - -# A workflow run is made up of one or more jobs that can run sequentially or in parallel -jobs: - # This workflow contains a single job called "build" - build: - # The type of runner that the job will run on - runs-on: ubuntu-latest - - # Steps represent a sequence of tasks that will be executed as part of the job - steps: - # Runs a set of commands using the runners shell - - name: Call Zapier web hook to close Asana task - if: ${{ !github.event.issue.pull_request }} - env: - ISSUE_TITLE: ${{ github.event.issue.title }} - run: | - curl --location --request POST 'https://hooks.zapier.com/hooks/catch/12728683/b7009qc/' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data-raw '{ - "task_name" : "$ISSUE_TITLE" - }' diff --git a/README.md b/README.md index b87c994a..0bab542a 100644 --- a/README.md +++ b/README.md @@ -83,6 +83,7 @@ OneSignal.init({ appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' }).then(() => { ``` ### Init Options + You can pass other [options](https://documentation.onesignal.com/docs/web-sdk-reference#init) to the `init` function. Use these options to configure personalized prompt options, auto-resubscribe, and more.
@@ -109,7 +110,7 @@ You can pass other [options](https://documentation.onesignal.com/docs/web-sdk-re | `[key: string]` | `any` | Additional properties can be added as needed. | **Service Worker Params** -You can customize the location and filenames of service worker assets. You are also able to specify the specific scope that your service worker should control. You can read more [here](https://documentation.onesignal.com/docs/onesignal-service-worker-faq#sdk-parameter-reference-for-service-workers). +You can customize the location and filenames of service worker assets. You are also able to specify the specific scope that your service worker should control. You can read more [here](https://documentation.onesignal.com/docs/onesignal-service-worker#custom-code-setup). In this distribution, you can specify the parameters via the following: @@ -124,7 +125,7 @@ In this distribution, you can specify the parameters via the following: ### Service Worker File -If you haven't done so already, you will need to add the [OneSignal Service Worker file](https://github.com/OneSignal/OneSignal-Website-SDK/files/11480764/OneSignalSDK-v16-ServiceWorker.zip) to your site ([learn more](https://documentation.onesignal.com/docs/web-push-quickstart#step-6-upload-files)). +If you haven't done so already, you will need to add the [OneSignal Service Worker file](https://github.com/OneSignal/OneSignal-Website-SDK/files/11480764/OneSignalSDK-v16-ServiceWorker.zip) to your site ([learn more](https://documentation.onesignal.com/docs/onesignal-service-worker#upload-the-js-file-to-your-server)). The OneSignal SDK file must be publicly accessible. You can put them in your top-level root or a subdirectory. However, if you are placing the file not on top-level root make sure to specify the path via the service worker params in the init options (see section above). @@ -194,9 +195,7 @@ OneSignal.Notifications.addEventListener('click', (event) => { }); ``` - - -See the [OneSignal WebSDK Reference](https://documentation.onesignal.com/docs/web-sdk-reference#addeventlistener-push-notification) for all available event listeners. +See the [OneSignal WebSDK Reference](https://documentation.onesignal.com/docs/web-sdk-reference#addeventlistener-notifications) for all available event listeners. ## Troubleshooting