From ff651f83547ac5c7b1982501a4157558fd822bdc Mon Sep 17 00:00:00 2001 From: Abhishek Y Date: Fri, 15 Mar 2024 07:21:47 +0530 Subject: [PATCH] Updated readme as per standard format --- LICENSE.md | 177 ++++++++++++++++++++++++++++++++++++++ README Old.md | 229 ++++++++++++++++++++++++++++++++++++++++++++++++++ README.md | 228 ++++++------------------------------------------- 3 files changed, 431 insertions(+), 203 deletions(-) create mode 100644 LICENSE.md create mode 100644 README Old.md diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 0000000..6b81a4b --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,177 @@ +## creative commons + +# Attribution-NonCommercial-ShareAlike 4.0 International + +Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible. + +### Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses. + +* __Considerations for licensors:__ Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. [More considerations for licensors](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensors). + +* __Considerations for the public:__ By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. [More considerations for the public](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensees). + +## Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. + +### Section 1 – Definitions. + +a. __Adapted Material__ means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. + +b. __Adapter's License__ means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. + +c. __BY-NC-SA Compatible License__ means a license listed at [creativecommons.org/compatiblelicenses](http://creativecommons.org/compatiblelicenses), approved by Creative Commons as essentially the equivalent of this Public License. + +d. __Copyright and Similar Rights__ means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. + +e. __Effective Technological Measures__ means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. + +f. __Exceptions and Limitations__ means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. + +g. __License Elements__ means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution, NonCommercial, and ShareAlike. + +h. __Licensed Material__ means the artistic or literary work, database, or other material to which the Licensor applied this Public License. + +i. __Licensed Rights__ means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. + +h. __Licensor__ means the individual(s) or entity(ies) granting rights under this Public License. + +i. __NonCommercial__ means not primarily intended for or directed towards commercial advantage or monetary compensation. For purposes of this Public License, the exchange of the Licensed Material for other material subject to Copyright and Similar Rights by digital file-sharing or similar means is NonCommercial provided there is no payment of monetary compensation in connection with the exchange. + +j. __Share__ means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. + +k. __Sui Generis Database Rights__ means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. + +l. __You__ means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. + +### Section 2 – Scope. + +a. ___License grant.___ + + 1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: + + A. reproduce and Share the Licensed Material, in whole or in part, for NonCommercial purposes only; and + + B. produce, reproduce, and Share Adapted Material for NonCommercial purposes only. + + 2. __Exceptions and Limitations.__ For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. + + 3. __Term.__ The term of this Public License is specified in Section 6(a). + + 4. __Media and formats; technical modifications allowed.__ The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material. + + 5. __Downstream recipients.__ + + A. __Offer from the Licensor – Licensed Material.__ Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. + + B. __Additional offer from the Licensor – Adapted Material.__ Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply. + + C. __No downstream restrictions.__ You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. + + 6. __No endorsement.__ Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). + +b. ___Other rights.___ + + 1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this Public License. + + 3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties, including when the Licensed Material is used other than for NonCommercial purposes. + +### Section 3 – License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the following conditions. + +a. ___Attribution.___ + + 1. If You Share the Licensed Material (including in modified form), You must: + + A. retain the following if it is supplied by the Licensor with the Licensed Material: + + i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of warranties; + + v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; + + B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and + + C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. + + 3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. + +b. ___ShareAlike.___ + +In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply. + + 1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-NC-SA Compatible License. + + 2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material. + + 3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply. + +### Section 4 – Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: + +a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database for NonCommercial purposes only; + +b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and + +c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. + +### Section 5 – Disclaimer of Warranties and Limitation of Liability. + +a. __Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.__ + +b. __To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.__ + +c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. + +### Section 6 – Term and Termination. + +a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. + +b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or + + 2. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or + + For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. + +c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. + +d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License. + +### Section 7 – Other Terms and Conditions. + +a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. + +b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. + +### Section 8 – Interpretation. + +a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. + +b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. + +c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. + +d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. + +``` +Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at [creativecommons.org/policies](http://creativecommons.org/policies), Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses. + +Creative Commons may be contacted at [creativecommons.org](http://creativecommons.org/). +``` \ No newline at end of file diff --git a/README Old.md b/README Old.md new file mode 100644 index 0000000..c633052 --- /dev/null +++ b/README Old.md @@ -0,0 +1,229 @@ +# BB Generic Client Layer + +## Overall Architecture + +Objective is to build domain-agnostic, reusable components for beckn applications, that can be configured and used across various domains. This requires a flexible and modular architecture, that can adapt to various domains with minimal code changes. + +![Architecture](architecture.png) + +The frontend (UI layer), and the backend-for-frontend (beckn client layer) should be assembled using building blocks. For example: a building block in the BFF is an API to process a search request, and a building block in the Frontend is a react component with search criteria, and display responses coming back from the API request. + +Each building block within the components can be dynamically enabled or disabled using feature toggles. + +## UI Components +There are multiple domain specific ecommerce UI apps, created using React. Domains are retail, mobility, healthcare, pharmacy, skilling etc. The UI is composed out of building blocks, that reduce repetitive coding. The UI components and app are in a monorepo. + +1. **Building Blocks Library:** + + - A centralized library of reusable building blocks/components for each domain will be created using React. + - These components will encapsulate domain-specific functionality and styling, reducing repetitive coding efforts. + +2. **Monorepo Structure:** + + - The UI components and apps will be organized in a monorepo for efficient code sharing and versioning. + - Each domain-specific app will be a separate package within the monorepo. + +3. **App Composition:** + + - Each domain-specific app will import and use the building blocks from the central library. + - These building blocks will be customized based on the specific needs of each domain. + +The UI interacts with 2 API backends, for beckn protocol and non-protocol interactions. + +### Non-Protocol Interactions + +The first backend supports non-protocol interactions, such as user registration, login, profile and order history. There could be documents attached to an user profile (example: resume). There could be documents attached to order history too (example: prescription, medical report or receipt). + + + +### Beckn-Protocol Interactions + +The second backend supports beckn protocol interactions. It offers a simplified API to UI apps, and converts the request into beckn protocol format, and makes a call to send or retrieve data from the beckn network. It also takes care of signing the payloads as required by beckn. + +![Generic Client Layer](client-layer-architecture.png) + +This client layer will offer a simplified synchronous API to the UI. It will expose REST APIs for the following operations: + +1. Search (search) +2. Add to Cart (select) +3. Checkout (init) +4. Place Order (confirm) +5. Track Order (status and track) +6. Update Order (update) +7. Cancel Order (cancel) +8. Customer Support (support) + +All these APIs will accept requests from multiple domains. BAP domain will be passed as a header parameter along with all the API requests. + +The API implementation will extract attributes from the request JSON, validate the values, and then transform the JSON into beckn protocol request structure. + +A JavaScript library will be created to transform a JSON input from one format to another based on mapping rules. This involves defining a mapping schema and implementing a function that applies these rules to transform the input JSON accordingly. This will be done in two steps: + +1. **Define the Mapping Rules:** + Define a mapping schema that outlines how the source JSON properties should be transformed to the target format. + +2. **Implement the Transformation Function:** + Create a function that iterates through the source JSON and applies the mapping rules to transform the JSON properties as per the schema. The logic to apply the mapping rules and transform the source JSON will be implemented accordingly. + +Here's a basic example (1:1 mapping) of a JavaScript method for JSON transformation based on mapping rules: + +```javascript +class JsonTransformer { + constructor(mappingSchema) { + this.mappingSchema = mappingSchema; + } + + transform(inputJson) { + if (!inputJson || typeof inputJson !== 'object') { + throw new Error('Input JSON is invalid.'); + } + + const transformedJson = {}; + + for (const key in this.mappingSchema) { + const sourceKey = this.mappingSchema[key]; + + // Apply transformation based on the mapping rules + transformedJson[key] = inputJson[sourceKey]; + } + + return transformedJson; + } +} + +// Example usage +const mappingSchema = { + 'newProperty1': 'oldProperty1', + 'newProperty2': 'oldProperty2' +}; + +const inputJson = { + 'oldProperty1': 'value1', + 'oldProperty2': 'value2' +}; + +const transformer = new JsonTransformer(mappingSchema); +const transformedJson = transformer.transform(inputJson); + +console.log(transformedJson); // Output: { newProperty1: 'value1', newProperty2: 'value2' } +``` + +The `JsonTransformer` class that takes a mapping schema during initialization and has a `transform` method to apply the mapping rules and transform the JSON based on those rules. The mapping schema and transformation logic will be implemented to process API requests for all domains. + +The `JsonTransformer` class can be enhanced to support multiple source-to-target mapping rules. It will also classify incoming JSON into a category based on a set criteria. The `transform` method will then apply the appropriate transformation rules based on the category. + +Here's the updated code: + +```javascript +class JsonTransformer { + constructor(mappingSchemas) { + this.mappingSchemas = mappingSchemas; + } + + classifyJson(json) { + // Implement your classification logic here based on the JSON structure or properties + // For simplicity, let's assume a property 'category' determines the category + return json.category; + } + + transform(inputJson) { + if (!inputJson || typeof inputJson !== 'object') { + throw new Error('Input JSON is invalid.'); + } + + const category = this.classifyJson(inputJson); + + if (!this.mappingSchemas[category]) { + throw new Error(`No mapping schema found for category: ${category}`); + } + + const mappingSchema = this.mappingSchemas[category]; + const transformedJson = {}; + + for (const targetKey in mappingSchema) { + const sourcePath = mappingSchema[targetKey].split('.'); + let sourceValue = inputJson; + + // Traverse the source path + for (const key of sourcePath) { + if (sourceValue && sourceValue.hasOwnProperty(key)) { + sourceValue = sourceValue[key]; + } else { + sourceValue = undefined; + break; + } + } + + // Assign the source value to the target key + transformedJson[targetKey] = sourceValue; + } + + return transformedJson; + } +} + +// Example usage +const mappingSchemas = { + 'category1': { + 'newProperty1': 'oldObject.oldProperty1', + 'newProperty2': 'oldObject.oldProperty2' + }, + 'category2': { + 'newPropertyA': 'oldPropertyA', + 'newPropertyB': 'oldPropertyB' + } +}; + +const inputJsonCategory1 = { + 'category': 'category1', + 'oldObject': { + 'oldProperty1': 'value1', + 'oldProperty2': 'value2' + } +}; + +const inputJsonCategory2 = { + 'category': 'category2', + 'oldPropertyA': 'valueA', + 'oldPropertyB': 'valueB' +}; + +const transformer = new JsonTransformer(mappingSchemas); + +const transformedJsonCategory1 = transformer.transform(inputJsonCategory1); +const transformedJsonCategory2 = transformer.transform(inputJsonCategory2); + +console.log('Transformed JSON for category 1:', transformedJsonCategory1); +console.log('Transformed JSON for category 2:', transformedJsonCategory2); +``` + +The `classifyJson` method is used to determine the category based on some criteria (e.g., a property named 'category' in the input JSON). The `transform` method then selects the appropriate mapping schema based on the category and applies the transformation accordingly. + + +## Feature Flag Service +This application has an UI that allows control of feature flags without changing the code by using a feature flag service. Administrators can toggle feature flags on or off dynamically without modifying the application's code. Toggle these flags on or off, change their targeting rules and validate results on the application. + +Feature flags are stored in the configuration management system. The frontend and backend applications fetch these configurations at runtime. The state of feature flags can be changed without re-deploying the application. + +## Sample Usage of Feature Flag in Node.js +``` +// Load configuration from a configuration file or environment variables +const featureConfig = { + searchEnabled: process.env.SEARCH_ENABLED === 'true', + // Add more feature flags as needed +}; + +// Middleware to parse JSON requests +app.use(bodyParser.json()); + +// Search endpoint +app.post('/api/search', (req, res) => { + if (!featureConfig.searchEnabled) { + return res.status(404).json({ message: 'Search feature is disabled' }); + } + + // Rest of your search logic +}); + +// Other endpoints and application logic +``` diff --git a/README.md b/README.md index c633052..f0daac2 100644 --- a/README.md +++ b/README.md @@ -1,48 +1,35 @@ -# BB Generic Client Layer +# Generic Client Layer -## Overall Architecture +## Introduction -Objective is to build domain-agnostic, reusable components for beckn applications, that can be configured and used across various domains. This requires a flexible and modular architecture, that can adapt to various domains with minimal code changes. +The Generic Client Layer acts as a crucial intermediary between the client (UI) and the protocol server, enabling the seamless transformation of data to meet the precise requirements of the client application. This layer takes on the responsibility of receiving data from the protocol server and meticulously processing it to align with the anticipated format, structure, and content mandated by the client interface. -![Architecture](architecture.png) - -The frontend (UI layer), and the backend-for-frontend (beckn client layer) should be assembled using building blocks. For example: a building block in the BFF is an API to process a search request, and a building block in the Frontend is a react component with search criteria, and display responses coming back from the API request. - -Each building block within the components can be dynamically enabled or disabled using feature toggles. - -## UI Components -There are multiple domain specific ecommerce UI apps, created using React. Domains are retail, mobility, healthcare, pharmacy, skilling etc. The UI is composed out of building blocks, that reduce repetitive coding. The UI components and app are in a monorepo. - -1. **Building Blocks Library:** - - - A centralized library of reusable building blocks/components for each domain will be created using React. - - These components will encapsulate domain-specific functionality and styling, reducing repetitive coding efforts. - -2. **Monorepo Structure:** - - - The UI components and apps will be organized in a monorepo for efficient code sharing and versioning. - - Each domain-specific app will be a separate package within the monorepo. +Overall, the Generic Client Layer plays a pivotal role in facilitating effective communication and data exchange between the client and server components of an application. Its optional integration, domain-agnostic nature, and versatility make it a valuable asset in modern software development environments. -3. **App Composition:** +## Release Notes - - Each domain-specific app will import and use the building blocks from the central library. - - These building blocks will be customized based on the specific needs of each domain. +Latest version: 1.1.0 -The UI interacts with 2 API backends, for beckn protocol and non-protocol interactions. +## Installation +To get started with this server, follow these steps: -### Non-Protocol Interactions +1. Clone the repository: `git clone https://github.com/beckn/generic-client-layer` +2. Install dependencies: `npm install` +3. Set up environment variables: Create a `.env` file based on the `.env.example` template and configure the required variables. +4. Start the server: `npm start` -The first backend supports non-protocol interactions, such as user registration, login, profile and order history. There could be documents attached to an user profile (example: resume). There could be documents attached to order history too (example: prescription, medical report or receipt). +## Usage - +- Run the server in development mode: `npm run dev` +- Run tests: `npm run test` +- Build the project: `npm run build` -### Beckn-Protocol Interactions +## Architecture +Objective is to build domain-agnostic, reusable components for beckn applications, that can be configured and used across various domains. This requires a flexible and modular architecture, that can adapt to various domains with minimal code changes. -The second backend supports beckn protocol interactions. It offers a simplified API to UI apps, and converts the request into beckn protocol format, and makes a call to send or retrieve data from the beckn network. It also takes care of signing the payloads as required by beckn. - -![Generic Client Layer](client-layer-architecture.png) +![Architecture](architecture.png) -This client layer will offer a simplified synchronous API to the UI. It will expose REST APIs for the following operations: +This client layer offers a simplified synchronous API from multiple domains to the UI. It exposes REST APIs for the following operations: 1. Search (search) 2. Add to Cart (select) @@ -52,178 +39,13 @@ This client layer will offer a simplified synchronous API to the UI. It will exp 6. Update Order (update) 7. Cancel Order (cancel) 8. Customer Support (support) +9. Rating (rate) -All these APIs will accept requests from multiple domains. BAP domain will be passed as a header parameter along with all the API requests. - -The API implementation will extract attributes from the request JSON, validate the values, and then transform the JSON into beckn protocol request structure. - -A JavaScript library will be created to transform a JSON input from one format to another based on mapping rules. This involves defining a mapping schema and implementing a function that applies these rules to transform the input JSON accordingly. This will be done in two steps: - -1. **Define the Mapping Rules:** - Define a mapping schema that outlines how the source JSON properties should be transformed to the target format. - -2. **Implement the Transformation Function:** - Create a function that iterates through the source JSON and applies the mapping rules to transform the JSON properties as per the schema. The logic to apply the mapping rules and transform the source JSON will be implemented accordingly. - -Here's a basic example (1:1 mapping) of a JavaScript method for JSON transformation based on mapping rules: - -```javascript -class JsonTransformer { - constructor(mappingSchema) { - this.mappingSchema = mappingSchema; - } - - transform(inputJson) { - if (!inputJson || typeof inputJson !== 'object') { - throw new Error('Input JSON is invalid.'); - } - - const transformedJson = {}; - - for (const key in this.mappingSchema) { - const sourceKey = this.mappingSchema[key]; - - // Apply transformation based on the mapping rules - transformedJson[key] = inputJson[sourceKey]; - } - - return transformedJson; - } -} - -// Example usage -const mappingSchema = { - 'newProperty1': 'oldProperty1', - 'newProperty2': 'oldProperty2' -}; - -const inputJson = { - 'oldProperty1': 'value1', - 'oldProperty2': 'value2' -}; - -const transformer = new JsonTransformer(mappingSchema); -const transformedJson = transformer.transform(inputJson); - -console.log(transformedJson); // Output: { newProperty1: 'value1', newProperty2: 'value2' } -``` - -The `JsonTransformer` class that takes a mapping schema during initialization and has a `transform` method to apply the mapping rules and transform the JSON based on those rules. The mapping schema and transformation logic will be implemented to process API requests for all domains. - -The `JsonTransformer` class can be enhanced to support multiple source-to-target mapping rules. It will also classify incoming JSON into a category based on a set criteria. The `transform` method will then apply the appropriate transformation rules based on the category. - -Here's the updated code: - -```javascript -class JsonTransformer { - constructor(mappingSchemas) { - this.mappingSchemas = mappingSchemas; - } - - classifyJson(json) { - // Implement your classification logic here based on the JSON structure or properties - // For simplicity, let's assume a property 'category' determines the category - return json.category; - } - - transform(inputJson) { - if (!inputJson || typeof inputJson !== 'object') { - throw new Error('Input JSON is invalid.'); - } - - const category = this.classifyJson(inputJson); - - if (!this.mappingSchemas[category]) { - throw new Error(`No mapping schema found for category: ${category}`); - } +## Link to Postman Collections - const mappingSchema = this.mappingSchemas[category]; - const transformedJson = {}; +[Postman Collection](https://github.com/beckn/generic-client-layer/blob/readme_update/postman/Generic%20Client%20Layer.postman_collection.json) - for (const targetKey in mappingSchema) { - const sourcePath = mappingSchema[targetKey].split('.'); - let sourceValue = inputJson; - // Traverse the source path - for (const key of sourcePath) { - if (sourceValue && sourceValue.hasOwnProperty(key)) { - sourceValue = sourceValue[key]; - } else { - sourceValue = undefined; - break; - } - } +## Transformation Layer - // Assign the source value to the target key - transformedJson[targetKey] = sourceValue; - } - - return transformedJson; - } -} - -// Example usage -const mappingSchemas = { - 'category1': { - 'newProperty1': 'oldObject.oldProperty1', - 'newProperty2': 'oldObject.oldProperty2' - }, - 'category2': { - 'newPropertyA': 'oldPropertyA', - 'newPropertyB': 'oldPropertyB' - } -}; - -const inputJsonCategory1 = { - 'category': 'category1', - 'oldObject': { - 'oldProperty1': 'value1', - 'oldProperty2': 'value2' - } -}; - -const inputJsonCategory2 = { - 'category': 'category2', - 'oldPropertyA': 'valueA', - 'oldPropertyB': 'valueB' -}; - -const transformer = new JsonTransformer(mappingSchemas); - -const transformedJsonCategory1 = transformer.transform(inputJsonCategory1); -const transformedJsonCategory2 = transformer.transform(inputJsonCategory2); - -console.log('Transformed JSON for category 1:', transformedJsonCategory1); -console.log('Transformed JSON for category 2:', transformedJsonCategory2); -``` - -The `classifyJson` method is used to determine the category based on some criteria (e.g., a property named 'category' in the input JSON). The `transform` method then selects the appropriate mapping schema based on the category and applies the transformation accordingly. - - -## Feature Flag Service -This application has an UI that allows control of feature flags without changing the code by using a feature flag service. Administrators can toggle feature flags on or off dynamically without modifying the application's code. Toggle these flags on or off, change their targeting rules and validate results on the application. - -Feature flags are stored in the configuration management system. The frontend and backend applications fetch these configurations at runtime. The state of feature flags can be changed without re-deploying the application. - -## Sample Usage of Feature Flag in Node.js -``` -// Load configuration from a configuration file or environment variables -const featureConfig = { - searchEnabled: process.env.SEARCH_ENABLED === 'true', - // Add more feature flags as needed -}; - -// Middleware to parse JSON requests -app.use(bodyParser.json()); - -// Search endpoint -app.post('/api/search', (req, res) => { - if (!featureConfig.searchEnabled) { - return res.status(404).json({ message: 'Search feature is disabled' }); - } - - // Rest of your search logic -}); - -// Other endpoints and application logic -``` +Jsonata is a powerful JavaScript library commonly employed for data transformation tasks. It enables one to define complex mapping rules, allowing for the seamless conversion of JSON data from one structure to another. By specifying a mapping schema, developers can instruct Jsonata on how to interpret and manipulate the input JSON, facilitating the transformation process. The library provides a robust set of functions and operators to handle various transformation scenarios, making it a versatile tool for data manipulation tasks. With Jsonata, developers can efficiently transform JSON data to meet the specific requirements of their applications, enhancing flexibility and interoperability.