npm - @convep_mobilogy/react-native-qms-plugin - Versions diffs - 1.9.0 → 1.9.2 - Mend

@convep_mobilogy/react-native-qms-plugin 1.9.0 → 1.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (3) hide show

package/QmsPluginFramework.podspec +1 -1
package/README.md +0 -163
package/package.json +1 -1

package/QmsPluginFramework.podspec CHANGED Viewed

@@ -7,6 +7,6 @@ Pod::Spec.new do |s|
   s.license = { :type => "Proprietary", :text => "Copyright © Convep Mobilogy. All rights reserved." }
   s.author = { "Convep Mobilogy" => "developer@convep.com" }
   s.platform = :ios, "15.1"
-  s.source = { :http => "https://sdk.convep.com/ios/QMS/qms-plugin/1.31.0", :type => "zip", :sha256 => "6bae9da81e3b0df77a98edf939279290990539e954407dae90904b96192705cf" }
+  s.source = { :http => "https://sdk.convep.com/ios/QOIOS/qms-plugin/1.31.0", :type => "zip", :sha256 => "6bae9da81e3b0df77a98edf939279290990539e954407dae90904b96192705cf" }
   s.vendored_frameworks = "QmsPluginFramework.xcframework"
 end

package/README.md CHANGED Viewed

@@ -2,47 +2,6 @@
 A React Native plugin that provides QMS (Quality Management System) components and APIs for defect management, dashboard visualization, and QMS workflow operations.
-## Development setup
-The development toolchain is managed with [mise](https://mise.jdx.dev/). From
-the repository root, install the pinned Node.js, Java, and Ruby versions and
-the JavaScript dependencies:
-```sh
-mise install
-mise run setup
-```
-The project pins Yarn through the `packageManager` field in `package.json`; the
-setup task enables Corepack before running the immutable Yarn install. Android
-SDK tooling and Xcode are platform dependencies and are not installed by mise.
-See [Contributing](CONTRIBUTING.md) for the complete development workflow and
-available mise tasks.
-To create a separate framework workspace with npm and local-development example
-apps, run:
-```sh
-./setup_framework.sh
-```
-The script confirms before moving this repository into a new
-`QmsPlugin_Framework` directory one level above its current location. See the
-contributing guide for the generated layout and non-interactive usage. It adds
-mise configuration to both generated apps and runs `mise install` plus
-`mise run setup` in the plugin and each app.
-For direct Kotlin/Java and Swift/Objective-C integration with the native AAR
-and XCFramework, see
-[Native QMS SDK Integration for Android and iOS](docs/ANDROID_IOS_INTEGRATION.md).
-For native Android development, AAR/Maven generation, example-app testing, and
-npm publishing, see
-[Android SDK Development and npm Release](docs/ANDROID_DEVELOPMENT_AND_RELEASE.md).
----
 # Installation
 Install using npm:
@@ -86,103 +45,6 @@ cd ios
 pod install
 ```
-## iOS framework development
-Use the following workflow when changing the native iOS framework and testing
-it in the included example app.
-### 1. Open the framework project
-Open the following project in Xcode and make the required native changes:
-```text
-framework/ios_framework/QmsPluginFramework.xcodeproj
-```
-### 2. Build and publish the XCFramework
-From the plugin root, run the build helper. It archives the framework for both
-iOS devices and the iOS Simulator, creates the XCFramework, packages it, and
-uploads the versioned ZIP used by the native CocoaPod:
-```sh
-./compile_framework.sh ios
-```
-You can optionally provide the SDK version:
-```sh
-./compile_framework.sh ios <sdk-version>
-```
-The versioned XCFramework ZIP and its SHA-256 checksum are written to
-`framework/ios_framework/build/releases/<sdk-version>/`. The root
-`QmsPluginFramework.podspec` is updated for the release. The native pod has no
-React dependency. The command uploads the ZIP to
-`https://sdk.convep.com/api/uploadIOS` using the same credentials and upload
-fields as Android. See [the iOS release guide](docs/IOS_COCOAPODS_RELEASE.md)
-for upload settings and the client Podfile.
-To build the XCFramework manually instead, run the following commands:
-```sh
-cd framework/ios_framework
-rm -rf QmsPluginFramework.xcframework
-xcodebuild archive \
-  -project QmsPluginFramework.xcodeproj \
-  -scheme QmsPluginFramework \
-  -destination "generic/platform=iOS" \
-  -archivePath ./build/ios_devices.xcarchive \
-  SKIP_INSTALL=NO \
-  BUILD_LIBRARY_FOR_DISTRIBUTION=YES
-xcodebuild archive \
-  -project QmsPluginFramework.xcodeproj \
-  -scheme QmsPluginFramework \
-  -destination "generic/platform=iOS Simulator" \
-  -archivePath ./build/ios_simulators.xcarchive \
-  SKIP_INSTALL=NO \
-  BUILD_LIBRARY_FOR_DISTRIBUTION=YES
-xcodebuild -create-xcframework \
-  -framework ./build/ios_devices.xcarchive/Products/Library/Frameworks/QmsPluginFramework.framework \
-  -framework ./build/ios_simulators.xcarchive/Products/Library/Frameworks/QmsPluginFramework.framework \
-  -output ./QmsPluginFramework.xcframework
-```
-### 3. Install the example app's iOS dependencies
-From the plugin root, run this after the uploaded version is available so
-CocoaPods downloads the latest native build:
-```sh
-cd example/ios
-pod install
-```
-### 4. Start Metro
-In a separate terminal, start Metro from the plugin root:
-```sh
-cd example
-npx react-native start
-```
-### 5. Build and run the example app
-Open the CocoaPods workspace (not the `.xcodeproj`) and run the desired iOS
-Simulator or connected device:
-```text
-example/ios/QmsPluginExample.xcworkspace
-```
-Repeat steps 2 through 5 after each native framework change.
----
 # Android Setup
 Autolinking should set up everything automatically, but you need to add the QMS
@@ -279,31 +141,6 @@ const styles = StyleSheet.create({
 ---
-## Open Add Issue Directly
-Use `QmsPlugin.openAddIssue` when the host app already knows the target unit and wants to skip the QMS project/unit/dashboard flow.
-```tsx
-import { QmsPlugin } from '@convep_mobilogy/react-native-qms-plugin';
-async function handleAddIssuePress() {
-  await QmsPlugin.openAddIssue({
-    userToken: '<UserToken>',
-    clientID: '<ClientID>',
-    clientCode: '<CompanyCode>',
-    isOrigin: false,
-    drawingPlanId: 1183,
-    projectId: 4,
-    unitName: 'C-L(7)',
-    projectName: 'Ara E Residence Dev',
-  });
-}
-```
-`drawingPlanId` is required because Add Issue needs a selected unit plan. `projectId`, `unitName`, and `projectName` are optional but recommended so the SDK can display and cache the correct context.
----
 # Props
 ## QmsDashboardView Props

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@convep_mobilogy/react-native-qms-plugin",
-  "version": "1.9.0",
+  "version": "1.9.2",
   "description": "To handle defect managment",
   "main": "./lib/module/index.js",
   "types": "./lib/typescript/src/index.d.ts",