Initial code drop

Author: b41ex

.eslintrc.json

@@ -0,0 +1,30 @@
+{
+  "root": true,
+  "env": {
+    "browser": true,
+    "es2020": true
+  },
+  "extends": [
+    "eslint:recommended",
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "ignorePatterns": [
+    "dist",
+    ".eslintrc.cjs"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "rules": {
+    "curly": "error",
+    "@typescript-eslint/no-explicit-any": "off",
+    "@typescript-eslint/no-unused-vars": "off",
+    "@typescript-eslint/ban-types": [
+      "error",
+      {
+        "types": {
+          "{}": false
+        },
+        "extendDefaults": true
+      }
+    ]
+  }
+}

.gitattributes

@@ -0,0 +1,24 @@
+*.js text eol=lf
+*.ts text eol=lf
+*.md text eol=lf
+*.yaml text eol=lf
+*.html text eol=lf
+*.json text eol=lf
+*.sh text eol=lf
+*.svg text eol=lf
+*.cjs text eol=lf
+.browserslistrc text eol=lf
+*.mp4 binary
+*.png binary
+*.jpg binary
+*.gif binary
+*.vsdx binary
+*.ttf binary
+*.eot binary
+*.woff binary
+*.woff2 binary
+.gitignore text eol=lf
+.npmignore text eol=lf
+.gitattributes text eol=lf
+LICENSE eol=lf
+NOTICE eol=lf

.gitignore

@@ -0,0 +1,14 @@
+node_modules/
+.env
+.vscode
+dist/
+.vuepress
+temp/
+browser
+coverage/
+.DS_store
+package-lock.json
+.yarnrc.yml
+.yarn
+*.iml
+/.idea/

CODE-OF-CONDUCT.md

@@ -0,0 +1,73 @@
+# Code of Conduct
+
+This repository is governed by following code of conduct guidelines.
+
+We put collaboration, trust, respect and transparency as core values for our community.
+Our community welcomes participants from all over the world with different experience,
+opinion and ideas to share.
+
+We have adopted this code of conduct and require all contributors to agree with that to build a healthy,
+safe and productive community for all.
+
+The guideline is aimed to support a community where all people should feel safe to participate,
+introduce new ideas and inspire others, regardless of:
+
+* Age
+* Gender
+* Gender identity or expression
+* Family status
+* Marital status
+* Ability
+* Ethnicity
+* Race
+* Sex characteristics
+* Sexual identity and orientation
+* Education
+* Native language
+* Background
+* Caste
+* Religion
+* Geographic location
+* Socioeconomic status
+* Personal appearance
+* Any other dimension of diversity
+
+## Our Standards
+
+We are welcoming the following behavior:
+
+* Be respectful for different ideas, opinions and points of view
+* Be constructive and professional
+* Use inclusive language
+* Be collaborative and show the empathy
+* Focus on the best results for the community
+
+The following behavior is unacceptable:
+
+* Violence, threats of violence, or inciting others to commit self-harm
+* Personal attacks, trolling, intentionally spreading misinformation, insulting/derogatory comments
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Derogatory language
+* Encouraging unacceptable behavior
+* Other conduct which could reasonably be considered inappropriate in a professional community
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of the Code of Conduct
+and are expected to take appropriate actions 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.
+
+## Reporting
+
+If you believe you’re experiencing unacceptable behavior that will not be tolerated as outlined above,
+please report to `[email protected]`. 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.
+
+Please also report if you observe a potentially dangerous situation, someone in distress, or violations of these guidelines,
+even if the situation is not happening to you.

CONTRIBUTING.md

@@ -0,0 +1,13 @@
+# Contribution Guide
+
+We'd love to accept patches and contributions to this project.
+Please, follow these guidelines to make the contribution process easy and effective for everyone involved.
+
+## Contributor License Agreement
+
+You must sign the [Contributor License Agreement](https://pages.netcracker.com/cla-main.html) in order to contribute.
+
+## Code of Conduct
+
+Please make sure to read and follow the [Code of Conduct](CODE-OF-CONDUCT.md).
+

LICENSE

@@ -1,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/

NOTICE

@@ -0,0 +1,7 @@
+qubership-apihub-api-unifier
+Copyright 2024-2025 NetCracker Technology Corporation
+
+This product includes software developed by https://github.com/udamir
+https://github.com/udamir/allof-merge
+MIT License
+Copyright (c) 2022 Damir Yusipov

README.md

@@ -1 +1,51 @@
-# qubership-apihub-api-unifier
+# qubership-apihub-api-unifier
+
+Unify API into a normalized presentation with all reference resolved, allOf combiners merged and other aspects unified.
+
+Supports OpenAPI and GraphQL specifications processing.
+
+## Modifications
+Modified version of [udamir/allof-merge](https://github.com/udamir/allof-merge)
+
+- Added cycles support during combiners resolve
+- Added origins support- it is now possible for any value in the unified JSO to track its origins in the source specification
+- Store original ref for the object if the object was resolved from ref
+- Gathered various API unification adapters from different libraries in the stack to a single place 
+- Support data structure hash calculation
+- Process different phases sequentially (reference resolving, allOf merge, unification)
+- Support synthetic `any` and `nothing` type for OAS
+- Added deprecated items calculation
+- Support new graphapi format
+- Feature flags added to control behavior during processing
+- Added a large number of tests
+- Debug tooling for cycled JSO
+
+## Features
+- Safe merging of schemas combined with allOf in whole document
+- Fastest implementation - up to x3 times faster then other popular libraries
+- Merged schema does not validate more or less than the original schema
+- Removes almost all logical impossibilities
+- Correctly merge additionalProperties, patternProperties and properties taking into account common validations
+- Correctly merge items and additionalItems taking into account common validations
+- Supports custom rules to merge other document types and JsonSchema versions
+- Supports input with circular references (javaScript references)
+- Supports $refs and circular $refs either (internal references only)
+- Correctly merge of $refs with sibling content (optionally)
+- Correctly merge of combiners (anyOf, oneOf) with sibling content (optionally)
+- Typescript syntax support out of the box
+- No dependencies (except json-crawl), can be used in NodeJS or browser
+
+## Works perfectly with specifications:
+
+- [JsonSchema](https://json-schema.org/draft/2020-12/json-schema-core.html)
+- [OpenApi 3.x](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md)
+- GraphApi
+- ~~Swagger 2.x~~ (roadmap)
+- ~~AsyncApi 2.x~~ (roadmap)
+- ~~AsyncApi 3.x~~ (roadmap)
+
+## Other libraries
+There are some libraries that can merge schemas combined with allOf. One of the most popular is [mokkabonna/json-schema-merge-allof](https://www.npmjs.com/package/json-schema-merge-allof), but it has some limitatons: Does not support circular $refs and no Typescript syntax out of the box.
+
+## External $ref
+If schema contains an external $ref, you should bundle it via [api-ref-bundler](https://github.com/udamir/api-ref-bundler) first.

SECURITY.md

@@ -0,0 +1,16 @@
+# Security Reporting Process
+
+Please, report any security issue to `[email protected]` where the issue will be triaged appropriately.
+
+If you know of a publicly disclosed security vulnerability please IMMEDIATELY email `[email protected]`
+to inform the team about the vulnerability, so we may start the patch, release, and communication process.
+
+# Security Release Process
+
+If the vulnerability is found in the latest stable release, then it would be fixed in patch version for that release.
+E.g., issue is found in 2.5.0 release, then 2.5.1 version with a fix will be released.
+By default, older versions will not have security releases.
+
+If the issue doesn't affect any existing public releases, the fix for medium and high issues is performed
+in a main branch before releasing a new version. For low priority issues the fix can be planned for future releases.
+

jest.config.ts

@@ -0,0 +1,23 @@
+module.exports = {
+  setupFilesAfterEnv: ['jest-extended/all'],
+  transform: {
+    '^.+\\.tsx?$': 'ts-jest',
+  },
+  testRegex: '(/tests/.*|(\\.|/)(test|spec))\\.(ts?|tsx?|js?|jsx?)$',
+  moduleFileExtensions: [
+    'ts',
+    'tsx',
+    'js',
+    'jsx',
+    'json',
+    'node',
+  ],
+  modulePathIgnorePatterns: [
+    '<rootDir>/dist/',
+  ],
+  // moduleNameMapper:{
+  // "^@netcracker/qubership-apihub-json-crawl$":'<rootDir>/../qubership-apihub-json-crawl/src',
+  // "^@netcracker/qubership-apihub-graphapi$":'<rootDir>/../qubership-apihub-graphapi/src',
+  // },
+  collectCoverage: true,
+}