kalai-attach 1.0.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,451 @@
+[![REUSE status](https://api.reuse.software/badge/github.com/cap-js/attachments)](https://api.reuse.software/info/github.com/cap-js/attachments)
+
+# Attachments Plugin
+
+The `kalai-attach` package is a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-packages) that provides out-of-the box asset storage and handling by using an [*aspect*](https://cap.cloud.sap/docs/cds/cdl#aspects) called `Attachments`. It also provides a CAP-level, easy-to-use integration of the [SAP Object Store](https://help.sap.com/docs/object-store/object-store-service-on-sap-btp/what-is-object-store).
+
+### Table of Contents
+
+<!-- TOC -->
+
+* [Usage](#usage)
+  * [Quick Start](#quick-start)
+  * [Local Walk-Through](#local-walk-through)
+  * [Changes in the CDS Models](#changes-in-the-cds-models)
+  * [Storage Targets](#storage-targets)
+  * [Malware Scanner](#malware-scanner)
+  * [Visibility Control](#visibility-control-for-attachments-ui-facet-generation)
+  * [Non-Draft Uploading](#non-draft-upload)
+* [Releases](#releases)
+* [Minimum UI5 and CAP NodeJS Version](#minimum-ui5-and-cap-nodejs-version)
+* [Architecture Overview](#architecture-overview)
+  * [Multitenancy](#multitenancy)
+  * [Object Stores](#object-stores)
+  * [Model Texts](#model-texts)
+* [Monitoring & Logging](#monitoring--logging)
+* [Support, Feedback, Contributing ](#support-feedback-and-contributing)
+* [Code of Conduct](#code-of-conduct)
+* [Licensing](#licensing)
+
+## Usage
+
+### Quick Start
+
+For a quick local development setup with in-memory storage:
+
+- The plugin is self-configuring as described, see the following details section. To enable attachments, simply add the plugin package to your project:  
+  ```sh
+  npm add kalai-attach
+  ```
+
+  <details>
+    The attachments plugin needs to be referenced in the package.json of the consuming CAP NodeJS application: 
+
+    ```cds
+    "devDependencies": { 
+      "kalai-attach": "<latest-version>", 
+      // (...)
+    }
+    ```
+
+    In addition, different profiles can be found in `package.json` as well, such as: 
+
+    ```json
+    "cds": {  
+      "requires": {  
+        // (...)
+        "[hybrid]": {  
+          "attachments": {  
+            "kind": "standard"  
+            // (...)
+          }  
+        }  
+      }  
+    }  
+    ```
+  </details>
+
+- To use Attachments, extend a CDS model by adding an element that refers to the pre-defined Attachments type (see [Changes in the CDS Models](#changes-in-the-cds-models) for more details): 
+
+  ```cds
+  using { Attachments } from 'kalai-attach';
+
+  entity Incidents {  
+      // (...)
+      attachments: Composition of many Attachments;  
+  }
+  ```
+
+In this guide, we use the [Incidents Management reference sample app](https://github.com/cap-js/incidents-app) as the base application to provide a demonstration how to use this plugin. A miniature version of this app can be found within the [tests](./tests/incidents-app) directory for local testing.
+
+For productive use, a valid object store binding is required, see [Object Stores](#object-stores) and [Storage Targets](#storage-targets).
+
+### Local Walk-Through
+
+With the steps above, we have successfully set up asset handling for our reference application. To test the application locally, use the following steps. 
+
+> [!NOTE]
+> For local testing, the attachment objects are stored in a [local database](https://cap.cloud.sap/docs/guides/databases-sqlite).
+
+1. **Start the server**:
+
+- *Default* scenario (In memory database):
+  ```sh
+  cds watch
+  ```
+
+2. **Navigate to the object page** of the incident `Solar panel broken`:
+Go to object page for incident **Solar panel broken**
+
+3. The `Attachments` type has generated an out-of-the-box Attachments table (see 1) at the bottom of the Object page:
+  <img width="1300" alt="Attachments Table" style="border-radius:0.5rem;" src="etc/facet.png">
+
+4. **Upload a file** by going into Edit mode and either using the **Upload** button on the Attachments table or by drag/drop. Then click the **Save** button to have that file stored that file in the dedicated resource (database, S3 bucket, etc.). We demonstrate this by uploading the PDF file from [_tests/integration/content/sample.pdf_](./tests/integration/content/sample.pdf):
+  <img width="1300" alt="Upload an attachment" style="border-radius:0.5rem;" src="etc/upload.gif">
+
+5. **Delete a file** by going into Edit mode, selecting the file, and pressing the **Delete** button above the Attachments table. Clicking the **Save** button will then delete that file from the resource (database, S3 bucket, etc.).
+  <img width="1300" alt="Delete an attachment" style="border-radius:0.5rem;" src="etc/delete.gif">
+
+### Changes in the CDS Models
+
+To use the aspect `Attachments` on an existing entity, the corresponding entity needs to either include attachments as an element in the model definition or be extended in a CDS file in the `srv` module. In the quick start, the former was done, adding an element to the model definition: 
+
+```cds
+using { Attachments } from 'kalai-attach';  
+
+entity Incidents {  
+  // ...  
+  attachments: Composition of many Attachments;  
+} 
+```
+ 
+The entity Incidents can also be extended in the `srv` module, as seen in the following example:
+
+```cds
+using { Attachments } from 'kalai-attach'; 
+
+extend my.Incidents with { 
+  attachments: Composition of many Attachments; 
+} 
+  
+service ProcessorService { 
+  entity Incidents as projection on my.Incidents 
+}
+```
+
+Both methods directly add the respective UI Facet. To use the plugin with an SAP Fiori elements UI, be sure that [`draft` is enabled](https://cap.cloud.sap/docs/advanced/fiori#enabling-draft-with-odata-draft-enabled) for the entity using `@odata.draft.enabled`. For example:
+
+```cds
+annotate service.Incidents with @odata.draft.enabled;
+```
+
+### Storage Targets
+
+When testing locally, the plugin operates without a dedicated storage target, storing attachments directly in the underlying database. In a hybrid setup, a dedicated storage target is preferred. You can bind it by using the `cds bind` command as described in the [CAP documentation for hybrid testing].(https://cap.cloud.sap/docs/advanced/hybrid-testing#services-on-cloud-foundry).
+
+Meanwhile, with a dedicated storage target the attachment is not stored in the underlying database; instead, it is saved on the specified storage target and only a reference to the file including metadata is kept in the database, as defined in the CDS model. 
+
+For using an Object Store in BTP, you must already have an SAP Object Store service instance on the appropriate landscape created. To bind it in a hybrid setup, follow this setup:
+
+1. Log in to Cloud Foundry:
+
+  ```sh
+  cf login -a <CF-API> -o <ORG-NAME> -s <SPACE-NAME> --sso
+
+2.  To bind to the service, generate a new file _.cdsrc-private.json in the project directory by running:
+
+  ```sh
+  cds bind <HybridObjectStoreName> --to <RemoteObjectStoreName>
+
+Where `HybridObjectStoreName` can be any name given by the user here and `RemoteObjectStoreName` is the name of your object store instance in SAP BTP.
+
+3.  To run the application in hybrid mode, run the command:
+
+```bash
+cds watch --profile hybrid
+```
+
+See [Object Stores](#object-stores) for further information on SAP Object Store.
+
+### Malware Scanner
+
+The BTP malware scanning service is used in the `AttachmentService` to scan attachments for vulnerabilities.
+
+For using [SAP Malware Scanning Service](https://discovery-center.cloud.sap/serviceCatalog/malware-scanning-service), you must already have a service instance which you can access. To bind it, run the following command:
+
+```sh
+cds bind <HybridMalwareScannerName> --to <RemoteMalwareScannerName>
+```
+
+By default, malware scanning is enabled for all profiles if a storage provider has been specified. You can configure malware scanning by setting:
+
+```json
+{  
+  "cds": {  
+     // (...)  
+     "attachments": {  
+       "scan": true  
+     }  
+  }  
+} 
+```
+
+If there is no malware scanner available and the scanner is not disabled, then the upload will fail. 
+
+Scan status codes: 
+- `Unscanned`: Attachment is still unscanned. 
+- `Scanning`: Immediately after upload, the attachment is marked as Scanning. Depending on processing speed, it may already appear as Clean when the page is reloaded. 
+- `Clean`: Only attachments with the status Clean are accessible. 
+- `Infected`: The attachment is infected. 
+- `Failed`: Scanning failed. 
+
+> [!Note]
+> The malware scanner supports mTLS authentication which requires an annual renewal of the certificate. Previously, basic authentication was used which has now been deprecated.
+
+> [!Note]
+> If the malware scanner reports a file size larger than the limit specified via [@Validation.Maximum](#specify-the-maximum-file-size) it removes the file and sets the status of the attachment metadata to failed.
+
+
+### Visibility Control for Attachments UI Facet Generation
+
+By setting the `@UI.Hidden` property to `true`, developers can hide the visibility of the plugin in the UI. This feature is particularly useful in scenarios where the visibility of the plugin needs to be dynamically controlled based on certain conditions.
+
+#### Example Usage
+
+```cds
+entity Incidents {
+  // ...
+  @UI.Hidden
+  attachments: Composition of many Attachments;
+}
+```
+
+In this example, the `@UI.Hidden` is set to `true`, which means the plugin will be hidden by default. You can also use dynamic expressions which are then added to the facet.
+
+```cds
+entity Incidents {
+  // ...
+  status : Integer enum {
+    submitted =  1;
+    fulfilled =  2;
+    shipped   =  3;
+    canceled  = -1;
+  };
+  @UI.Hidden : (status = #canceled ? true : false)
+  attachments: Composition of many Attachments;
+}
+```
+
+### Non-Draft Upload
+
+For scenarios where the entity is not draft-enabled, for example [`tests/non-draft-request.http`](./tests/non-draft-request.http), separate HTTP requests for metadata creation and asset uploading need to be performed manually. 
+
+The typical sequence includes:
+
+1. **POST** -> create attachment metadata, returns ID  
+2. **PUT** -> upload file content using the ID
+
+### Specify the maximum file size
+
+You can specify the maximum file size by annotating the attachments content property with `@Validation.Maximum`
+
+```cds
+entity Incidents {
+  ...
+  attachments: Composition of many Attachments;
+}
+
+annotate Incidents.attachments with {
+  content @Validation.Maximum : '20MB';
+}
+```
+
+The default is 400MB
+
+### Restrict allowed MIME types
+
+You can restrict which MIME types are allowed for attachments by annotating the content property with `@Core.AcceptableMediaTypes`. This validation is performed during file upload.
+
+```cds
+entity Incidents {
+  ...
+  attachments: Composition of many Attachments;
+}
+
+annotate Incidents.attachments with {
+  content @Core.AcceptableMediaTypes : ['image/jpeg', 'image/png', 'application/pdf'];
+}
+```
+
+Wildcard patterns are supported:
+
+```cds
+annotate Incidents.attachments with {
+  content @Core.AcceptableMediaTypes : ['image/*', 'application/pdf'];
+}
+```
+
+To allow all MIME types (default behavior), either omit the annotation or use:
+
+```cds
+annotate Incidents.attachments with {
+  content @Core.AcceptableMediaTypes : ['*/*'];
+}
+```
+
+When a file with a disallowed MIME type is uploaded, the request will be rejected with a `400` error.
+
+## Releases
+
+- The plugin is released to [NPM Registry](https://www.npmjs.com/package/kalai-attach).
+- See the [changelog](./CHANGELOG.md) or [GitHub Releases](https://github.com/cap-js/attachments/releases) for the latest changes.
+
+## Minimum UI5 and CAP NodeJS Version
+
+| Component | Minimum Version |
+|-----------|-----------------|
+| CAP Node  | 8.0.0           |
+| UI5       | 1.136.0         |
+
+## Architecture Overview
+### Multitenancy
+
+The plugin supports multi-tenancy scenarios, allowing both shared and tenant-specific object store instances.
+
+> [!Note]
+> Starting from version 2.1.0, **separate mode** for object store instances is the default setting for multi-tenancy.  
+
+For multi-tenant applications, `kalai-attach` must be included in the dependencies of both the application-level and _mtx/sidecar/package.json_ files.
+
+#### Separate object store instances
+
+By default the plugin creates for each tenant its own object store instance during the tenants subscription.
+
+When the tenant unsubscribes the object store instance is deleted.
+
+> [!WARNING]
+> When you remove the plugin from an application after separate object stores already have been created, the object stores are not automatically removed!
+
+#### Shared Object Store Instance
+
+To configure a shared object store instance, modify both the package.json files as follows:
+
+```json
+"cds": {
+  "requires": {
+    "attachments": {
+      "objectStore": {
+        "kind": "shared"
+      }
+    }
+  }
+}
+```
+To ensure tenant identification when using a shared object store instance, the plugin prefixes attachment URLs with the tenant ID. Be sure the shared object store instance is bound to the `mtx` application module before deployment.
+
+### Object Stores
+
+A valid object store service binding is required, typically one provisioned through SAP BTP. See [Storage Targets](#storage-targets) and [Deployment to Cloud Foundry](#deployment-to-cloud-foundry) on how to use this object store service binding.
+
+#### Deployment to Cloud Foundry
+
+The corresponding entry in the [mta-file](https://cap.cloud.sap/docs/guides/deployment/to-cf#add-mta-yaml) possibly looks like:
+
+```
+_schema-version: '0.1'
+ID: consuming-app
+version: 1.0.0
+description: "App consuming the attachments plugin with an object store"
+parameters:
+  ...
+modules:
+  - name: consuming-app-srv
+# ------------------------------------------------------------
+    type: nodejs
+    path: srv
+    parameters:
+      ...
+    properties:
+      ...
+    build-parameters:
+      ...
+    requires:
+      - name: consuming-app-hdi-container
+      - name: consuming-app-uaa
+      - name: cf-logging
+      - name: **object-store-service**
+...
+resources:
+  ...
+  - name: **object-store-service**
+    type: org.cloudfoundry.managed-service
+    parameters:
+      service: objectstore
+      service-plan: standard
+```
+
+
+##### Tests
+
+The unit tests in this module do not need a binding to the respective object stores, run them with `npm install`. To achieve a clean install, the command `rm -rf node_modules` should be used before installation.
+
+The integration tests need a binding to a real object store. Run them with `npm run test`.
+To set the binding, please see the section [Storage Targets](#storage-targets).
+
+##### Supported Storage Provider
+
+- **Standard** (`kind: "standard"`) | Depending on the bound object store credentials, uses AWS S3, Azure Blob Storage or GCP Cloud Storage. You can manually specify the implementation by adjusting the type to:
+    - **AWS S3** (`kind: "s3"`)
+    - **Azure Blob Storage** (`kind: "azure"`)
+    - **GCP Cloud Storage** (`kind: "gcp"`)
+
+### Model Texts
+
+In the model, several fields are annotated with the `@title` annotation. Default texts are provided in [2 languages](./_i18n). If these defaults are not sufficient for an application, they can be overwritten by applications with custom texts or translations.
+
+The following table gives an overview of the fields and the i18n codes:
+
+| Field Name | i18n Code    |
+|------------|--------------|
+| `mimeType` | `MediaType`  |
+| `fileName` | `FileName`   |
+| `status`   | `ScanStatus` |
+| `note`     | `note`       |
+
+In addition to the field names, header information (`@UI.HeaderInfo`) are also annotated:
+
+| Header Info      | i18n Code     |  
+|------------------|---------------|
+| `TypeName`       | `Attachment`  |
+| `TypeNamePlural` | `Attachments` |
+
+
+## Monitoring & Logging
+
+To configure logging for the attachments plugin, add the following configuration to the `package.json` of the consuming application:
+
+```json
+{
+  "cds": {
+    "log": {
+      "levels": {
+         // (...)
+         "attachments": "debug"
+      }
+    }
+  }
+}
+...
+```
+
+## Support, Feedback, and Contributing 
+
+This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/cap-js/attachments/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, the **local development setup**, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).
+
+## Code of Conduct
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its [Code of Conduct](CODE_OF_CONDUCT.md) at all times.
+
+## Licensing
+
+Copyright 2024 SAP SE or an SAP affiliate company and contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/cap-js/attachmentstea).

package/_i18n/i18n.properties

@@ -0,0 +1,6 @@
+Attachment=Attachment
+Attachments=Attachments
+Note=Note
+ScanStatus=Scan status
+FileName=File name
+MediaType=Media type

package/_i18n/i18n_ar.properties

@@ -0,0 +1,6 @@
+Attachment=\u0627\u0644\u0645\u0631\u0641\u0642
+Attachments=\u0627\u0644\u0645\u0631\u0641\u0642\u0627\u062A
+Note=\u0645\u0644\u0627\u062D\u0638\u0629
+ScanStatus=\u062D\u0627\u0644\u0629 \u0627\u0644\u0645\u0633\u062D \u0627\u0644\u0636\u0648\u0626\u064A
+FileName=\u0627\u0633\u0645 \u0627\u0644\u0645\u0644\u0641
+MediaType=\u0646\u0648\u0639 \u0627\u0644\u0648\u0633\u0627\u0626\u0637

package/_i18n/i18n_bg.properties

@@ -0,0 +1,6 @@
+Attachment=\u041F\u0440\u0438\u043B\u043E\u0436\u0435\u043D\u0438\u0435
+Attachments=\u041F\u0440\u0438\u043B\u043E\u0436\u0435\u043D\u0438\u044F
+Note=\u0417\u0430\u0431\u0435\u043B\u0435\u0436\u043A\u0430
+ScanStatus=\u0421\u0442\u0430\u0442\u0443\u0441 \u043D\u0430 \u0441\u043A\u0430\u043D\u0438\u0440\u0430\u043D\u0435
+FileName=\u0418\u043C\u0435 \u043D\u0430 \u0444\u0430\u0439\u043B
+MediaType=\u0412\u0438\u0434 \u043C\u0435\u0434\u0438\u044F

package/_i18n/i18n_cs.properties

@@ -0,0 +1,6 @@
+Attachment=P\u0159\u00EDloha
+Attachments=P\u0159\u00EDlohy
+Note=Pozn\u00E1mka
+ScanStatus=Status skenov\u00E1n\u00ED
+FileName=N\u00E1zev souboru
+MediaType=Typ m\u00E9dia