@sap/wing-service-explorer - npm Package Compare versions

Comparing version 1.6.1 to 1.6.7

dist/lib/metadata/metadataExplorerType.d.ts

@@ -46,3 +46,3 @@ export interface EntitySetPropertyType {
      * In case of complex types, should show containing properties. Can be recursive.
-     * For complex types show with slashes(see attached email) in https://sapjira.wdf.sap.corp/browse/DEVXCORE-1810.
+     * For complex types show with slashes.
      * Complex types will be implemented in further stage.
@@ -49,0 +49,0 @@ * Currently, don't return properties of complex types.

dist/lib/metadata/metadataFactory.js

@@ -30,3 +30,3 @@ "use strict";
         this.logger.info(this.getMetadataExplorer.name, { edmxVersion });
-        // V4 is implemented firstly. Details: https://sapjira.wdf.sap.corp/browse/DEVXCORE-1810
+        // V4 is implemented firstly.
         // TBD: After implementing V2, should be changed to return correct object.
@@ -33,0 +33,0 @@ if (edmxVersion === MetadataFactory.VERSION4) {

dist/lib/mockups/listDestinations.json

@@ -86,3 +86,3 @@ [
         "WebIDEEnabled": "true",
-        "Host": "http://github-wdf-dummy-url:443",
+        "Host": "http://github-dummy-url:443",
         "WebIDEExposedHost": "github-wdf-dummy-url"
@@ -97,5 +97,5 @@ },
         "WebIDEEnabled": "true",
-        "Host": "http://nexus.wdf.sap.corp:8081",
-        "WebIDEExposedHost": "nexus.wdf.sap.corp:8081"
+        "Host": "http://nexus.dummy.com:8081",
+        "WebIDEExposedHost": "nexus.dummy.com:8081"
     }
 ]

package.json

 {
   "name": "@sap/wing-service-explorer",
-  "version": "1.6.1",
+  "version": "1.6.7",
   "description": "Provide the ability to explore SAP services",
   "license": "See LICENSE.txt",
   "author": "SAP SE",
-  "repository": {
-    "type": "git",
-    "url": "https://github.wdf.sap.corp/DevX/wing-service-explorer"
-  },
   "keywords": [],
   "files": [
-    "**/*.js",
-    "**/*.json",
-    "**/*.xml",
-    "**/*.d.ts"
+    "dist/**/*"
   ],
@@ -41,3 +34,3 @@ "main": "dist/lib/index.js",
   "devDependencies": {
-    "@sap/consume-services-types": "0.3.6",
+    "@sap/consume-services-types": "0.3.11",
     "@types/chai": "^4.1.7",
@@ -44,0 +37,0 @@ "@types/fs-extra": "^8.0.0",

README.md

@@ -1,8 +0,1 @@
-[![Build Status](https://gkeplatform2.jaas-gcp.cloud.sap.corp/buildStatus/icon?job=wing-service-explorer-ci%2Fmaster)](https://gkeplatform2.jaas-gcp.cloud.sap.corp/job/wing-service-explorer-ci/job/master/)
-[![Build Status](https://prod-build10100.wdf.sap.corp:443/buildStatus/icon?job=devx-wing%2Fdevx-wing-wing-service-explorer-SP-REL-common_indirectshipment)](https://prod-build10100.wdf.sap.corp:443/job/devx-wing/job/devx-wing-wing-service-explorer-SP-REL-common_indirectshipment/)
-[![Coverage](https://sonar.wdf.sap.corp/api/project_badges/measure?project=devxwing-service-explorer&metric=coverage)](https://sonar.wdf.sap.corp/dashboard?id=devxwing-service-explorer)
-[![Maintainability Rating](https://sonar.wdf.sap.corp/api/project_badges/measure?project=devxwing-service-explorer&metric=sqale_rating)](https://sonar.wdf.sap.corp/dashboard?id=devxwing-service-explorer)
-[![Code Smells](https://sonar.wdf.sap.corp/api/project_badges/measure?project=devxwing-service-explorer&metric=code_smells)](https://sonar.wdf.sap.corp/dashboard?id=devxwing-service-explorer)
-[![Duplicated Lines (%)](https://sonar.wdf.sap.corp/api/project_badges/measure?project=devxwing-service-explorer&metric=duplicated_lines_density)](https://sonar.wdf.sap.corp/dashboard?id=devxwing-service-explorer)
-[![Vulnerabilities](https://sonar.wdf.sap.corp/api/project_badges/measure?project=devxwing-service-explorer&metric=vulnerabilities)](https://sonar.wdf.sap.corp/dashboard?id=devxwing-service-explorer)
 
@@ -14,8 +7,3 @@ # @sap/wing-service-explorer
 **Wing-service-explorer** is an npm package that provides the ability to explore SAP services.
-This Readme file explains how to setup the development environment, how the development process and tests are performed, and how to release the feature in Nexus.
 
-## Usage
-
-To add this package as a dependency in your **package.json** file, under the "dependencies" section, add the following dependency: `"@sap/wing-service-explorer": [Version]`
-
 ## API
@@ -78,71 +66,1 @@
 Returns a list of destinations which contain an additional property named **XFSystemName**.
-
-## Development Process
-
-### GIT and GitHub
-
-1. Open Git Bash, go to the local repository directory and sync with the remote repository.
-2. Develop in a **Local** branch.
-
-- Create a new descriptive branch `git checkout -b my-local-branch-name` <br>**OR** rename the previous one `git branch -m my-local-branch-name`.
-- Make sure _my-local-branch-name_ is **NOT master** and that there is **no existing** branch with this name.
-
-3. Sync with the remote repository.
-
-- Fetch the code from the master branch by running `git fetch; git merge`.
-
-4. Make your local changes.
-
-- Run `npm install` to install dependencies.
-- Run `npm run test` to compile the typescript code to JS and run tests.
-
-5. Commit and push.
-
-- **Do not push directly to master !!!**
-- Commit your changes and push to create a new branch on GitHub by running `git push origin my-local-branch-name`
-- On consecutive commits **DO NOT** use `commit ammend`. You should create a new commit and push to the same feature branch again. This will add an extra commit to your pull request and retrigger the voters.
-
-6. Open the [repository](https://github.wdf.sap.corp/devx-wing/wing-service-explorer) on GitHub and go to **Code > Branches**.
-7. Open a pull request.
-
-- Click ![image](https://github.wdf.sap.corp/storage/user/15516/files/f0632932-b48b-11e6-8c87-75a073ff4b9f) next to your branch.
-- Edit the pull request name with BLI or BCP. For example: _"BLI DEVXCORE-123: my new feature"_ or _"BCP 1670451810: Fix my bug"_.
-- A new branch _my-local-branch-name_ is created in the GitHub repository.
-- The new code should enable all voters and code review to pass successsfully.
-
-8. Update the existing pull request.
-
-- Stage your changes and create a new commit.
-- Perform Git fetch
-- Perform Git merge on origin/master - merge your changes with the most updated master branch.
-- Push your changes to your _my-local-branch-name_ (Git push origin _my-local-branch-name_).
-
-9. Merge the pull request.
-
-- If all voters passed (XMake + JaaS Voter) click ![image](https://github.wdf.sap.corp/storage/user/15516/files/a1501da6-b6fb-11e6-9240-37aa1b14409c) (which should become green).
-- If your pull request contains several commits, you can put them together in one commit from GitHub by selecting the ![image](https://github.wdf.sap.corp/storage/user/15516/files/c6415274-b6fb-11e6-98a6-d417a638b013) option from the Merge dropdown list.
-
-10. Delete your branch.
-
-- Once merge is complete, go to **Code > Branches**.
-- Look for your merged pull request and click ![image](https://github.wdf.sap.corp/storage/user/15516/files/a4ac4604-b48b-11e6-84c7-8423bde60ec8).
-
-### Tests and Coverage
-
-- Run `npm run test` to run the Unit tests written in Mocha as well as the coverage test.
-
-## Release
-
-1. Bump the version in the exposed ports github file.
-
-- [package.json](https://github.wdf.sap.corp/devx-wing/wing-service-explorer/blob/master/package.json#L5).
-
-
-    **_Notes:_**
-    Make sure to follow this versioning concept:
-    - When providing new features (as when releasing at end of the sprint or when a new feature is ready), bump a major version (e.g: from 1.1.0 to 1.2.0).
-    - When providing a bug fix to an existing version ("hot fix"), bump a minor version (e.g: from 1.1.0 to 1.1.1).
-
-2. Use [XMAKE Release Job](https://prod-build10100.wdf.sap.corp/job/devx-wing/job/devx-wing-wing-service-explorer-SP-REL-common_indirectshipment/) (Stage and promote) to upload a new version to Nexus (based on master).
-   The XMAKE Release Job currently runs automatically on merge.
-   3 The newly released version location in [nexus](http://nexus.wdf.sap.corp:8081/nexus/content/repositories/build.releases/com/sap/npm/wing-service-explorer/)

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Improved metrics

Number of low supply chain risk alerts

2

decreased by-33.33%

Worsened metrics

Total package byte prevSize

326039

decreased by-77.49%

Number of package files

45

decreased by-53.12%

Lines of code

5958

decreased by-67.06%

Number of lines in readme file

65

decreased by-55.78%

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes