chore: format codebase with vite-plus formatter

Author: fadi-george

.github/ISSUE_TEMPLATE/ask-question.yml

@@ -1,7 +1,7 @@
 name: 🙋‍♂️ Ask a question
 description: Tell us what's on your mind
-title: "[Question]: "
-labels: ["Question"]
+title: '[Question]: '
+labels: ['Question']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,7 +1,7 @@
 name: 🪳 Bug Report
 description: File a bug report
-title: "[Bug]: "
-labels: ["Bug"]
+title: '[Bug]: '
+labels: ['Bug']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/general-feedback.yml

@@ -1,7 +1,7 @@
 name: 📣 General feedback
 description: Tell us what's on your mind
-title: "[Feedback]: "
-labels: ["Feedback"]
+title: '[Feedback]: '
+labels: ['Feedback']
 body:
   - type: markdown
     attributes:

.github/pull_request_template.md

@@ -1,46 +1,57 @@
 <!-- START -->
+
 # READ AND DELETE THIS SECTION BEFORE SUBMITTING PR
-* **Fill out each _REQUIRED_ section**
-* **Fill out _OPTIONAL_ sections, remove section if it doesn't apply to your PR**
-* **Read and fill out each of the checklists below**
-* **Remove this section after reading**
+
+- **Fill out each _REQUIRED_ section**
+- **Fill out _OPTIONAL_ sections, remove section if it doesn't apply to your PR**
+- **Read and fill out each of the checklists below**
+- **Remove this section after reading**
 <!-- END -->
 
 # Description
+
 ## One Line Summary
+
 **REQUIRED** - Very short description that summaries the changes in this PR.
 
 ## Details
 
 ### Motivation
+
 **REQUIRED -** Why is this code change being made? Or what is the goal of this PR? Examples: Fixes a specific bug, provides additional logging to debug future issues, feature to allow X.
 
 ### Scope
+
 **RECOMMEND - OPTIONAL -** What is intended to be effected. What is known not to change. Example: Notifications are grouped when parameter X is set, not enabled by default.
 
 ### OPTIONAL - Other
+
 **OPTIONAL -** Feel free to add any other sections or sub-sections that can explain your PR better.
 
 # Testing
 
 ## Manual testing
-**REQUIRED -** Explain what scenarios were tested and the environment.
 
+**REQUIRED -** Explain what scenarios were tested and the environment.
 
 # Checklist
+
 ## Overview
-   - [ ] I have filled out all **REQUIRED** sections above
-   - [ ] PR does one thing
-     - If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
-   - [ ] Any Public API changes are explained in the PR details and conform to existing APIs
+
+- [ ] I have filled out all **REQUIRED** sections above
+- [ ] PR does one thing
+  - If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
+- [ ] Any Public API changes are explained in the PR details and conform to existing APIs
 
 ## Testing
-   - [ ] I have personally tested this on my device, or explained why that is not possible
-   - [ ] I have tested this on the latest version of the plugin
-   - [ ] I have tested this on both Android and iOS, or explained why that is not possible
+
+- [ ] I have personally tested this on my device, or explained why that is not possible
+- [ ] I have tested this on the latest version of the plugin
+- [ ] I have tested this on both Android and iOS, or explained why that is not possible
 
 ## Final pass
-   - [ ] Code is as readable as possible.
-      - Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
-   - [ ] I have reviewed this PR myself, ensuring it meets each checklist item
-      - WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.
+
+- [ ] Code is as readable as possible.
+  - Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
+- [ ] I have reviewed this PR myself, ensuring it meets each checklist item
+  - WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

.github/workflows/claude-code-review.yml

@@ -41,4 +41,3 @@ jobs:
           prompt: '/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}'
           # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
           # or https://code.claude.com/docs/en/cli-reference for available options
-

.github/workflows/claude.yml

@@ -47,4 +47,3 @@ jobs:
           # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
           # or https://code.claude.com/docs/en/cli-reference for available options
           # claude_args: '--allowed-tools Bash(gh pr:*)'
-

.vscode/extensions.json

@@ -1,5 +1,3 @@
 {
-  "recommendations": [
-    "VoidZero.vite-plus-extension-pack"
-  ]
+  "recommendations": ["VoidZero.vite-plus-extension-pack"]
 }

CHANGELOG.md

@@ -1,100 +1,145 @@
 # Changelog
+
 All notable changes to this project will be documented in this file.
 
 ## October 2023
+
 ### `2.0.2` - 10/16/23
+
 #### Changes
+
 - Move target check to top of function to avoid adding duped PBXGroup
 
 ## September 2023
+
 ### `2.0.1` - 09/27/23
+
 #### Changes
+
 - Plugin Prop Validation & Improvements
 - Add ability to set the small icon accent color
 - Update Usage in README to reflect major release changes
 
 ### `2.0.0` - 09/12/23
+
 #### Changes
+
 - Native version update & major release
 - Bump word-wrap from 1.2.3 to 1.2.4
 
 ## April 2023
+
 ### `1.3.2` - 04/18/23
+
 #### Changes
+
 - Update iOS generation to write xcode project via expo mod rather than directly to file system.
 - Bump qs from 6.5.2 to 6.5.3
-- Bump decode-uri-component from 0.2.0 to 0.2.2 
+- Bump decode-uri-component from 0.2.0 to 0.2.2
 - Bump @xmldom/xmldom from 0.7.5 to 0.7.10
 - Bump multiple dependency versions in OneSignal Example App (ua-parser-js, decode-uri-component, @sideway/formula, @xmldom/xmldom)
 
 ## March 2023
+
 ### `1.3.1` - 03/03/23
+
 #### Changes
+
 - Update monorepo logic to rely on the more reliable `require.resolve` to find the `onesignal-expo-plugin` package.
 
 ## November 2022
+
 ### `1.3.0` - 11/30/22
+
 #### Changes
+
 - Add `iosNSEFilePath` configuration options to the plugin, which allows an app to specify a custom iOS Notification Service Extension.
 
 ## October 2022
+
 ### `1.2.0` - 10/25/22
+
 #### Changes
+
 - Add `smallIcons` and `largeIcons` configuration options to the plugin, which allows an app to specify large and small notification icons to package within the Android build.
 - Bump jpeg-js from 0.4.3 to 0.4.4
 - Bump simple-plist from 1.3.0 to 1.3.1
 
 ### `1.1.2` - 10/04/22
+
 #### Fixes
+
 - Specify `use_frameworks` on `OneSignalNotificationServiceExtension` target in iOS Podfile when applicable (i.e. the app target also specifies `use_frameworks`).
 
 ## September 2022
+
 ### `1.1.1` - 09/06/22
+
 #### Fixes
+
 - Fix issue where EAS release builds were no longer successfully building due to log statement
 
 ### `1.1.0` - 09/01/22
+
 #### Changes
+
 - No longer inject the OneSignal Gradle plugin on Android builds
+
 #### Fixes
+
 - Fix issue where plugin does not support monorepos
 
 ## April 2022
+
 ### `1.0.1` - 04/11/22
 
 #### Changes
+
 - Add more info regarding the `expo prebuild` command to README.
+
 #### Fixes
+
 - Upstream EAS workaround for "Missing Push Capability on iOS" issue. Adds `aps-environment` entitlement to NSE template. Although it is **not** required in normal builds, there is an upstream limitation from EAS that is resolved by including the push entitlement in both target entitlement files. As of 4/8/22, EAS builds will randomly pick an entitlement file if there are multiple in a project without differentiating among targets. This is resulting in flaky builds where half the time they work and half the time they don't. This can be seen as a temporary fix. Note it carries no side-effects / repercussions (i.e: the entitlement is superfluous but not critical to remove in the future).
 
 ## March 2022
+
 ### `1.0.0` - 03/28/22
 
 #### Fixes
+
 - Upgrade dependencies (via dependabot)
+
 #### Changes
+
 - Add credentials guide and update README
 - Advance to General Availability
 
 ## February 2022
+
 ### `1.0.0-beta11` - 02/18/2022
+
 #### Added
+
 - Linting
 - Instead of creating a "WriterManager", we repurpose the ReaderManager class by renaming it to FileManager and adding a synchronized write helper function (synchronous in the sense that it block further execution until complete).
 - iOS constants file
 
 #### Fixes
+
 - Import cleanups
 - Linting errors
 - Write safety issu. NSE updater helper functions were previously writing to the entitlements & plist files asynchronously. We should await on each to ensure we don't have multiple writes to the same file at once (which is unsafe).
 
 ## January 2022
 
 ### `1.0.0-beta10` - 01/24/2022
+
 #### Added
+
 - ability to configure version numbers used in the NSE target's plist file.
 - `OneSignalLog` class for better console logging.
 - this changelog file.
 
 #### Fixed
+
 - re-running `expo prebuild` will no longer result in duplicate entitlements and dependencies added to native files.

EAS.md

@@ -1,17 +1,21 @@
 # Expo Application Services
+
 EAS is Expo's cloud-build service.
 
 ## [EAS Homepage](https://expo.dev/eas)
 
 ## EAS + OneSignal Setup
+
 To get OneSignal push notifications working in an EAS-built app, see our guide on how to configure your [iOS credentials](IOS_CREDENTIALS_EAS.md).
 
 ## How to run an iOS EAS-built app
+
 ### Run in a production environment
-For production builds, your generated ipa file should to be distributed to the App Store or Testflight.
 
+For production builds, your generated ipa file should to be distributed to the App Store or Testflight.
 
 ### Run in custom development client
+
 For development/internal distribution builds, you will need to install a [development client](https://docs.expo.dev/development/getting-started/) on your iOS device.
 
 1. Scan the QR code shown in the terminal after EAS build success and install the development client application to your device.