1c/OpenIntegrations
1
0
Fork 0
mirror of https://github.com/Bayselonarrend/OpenIntegrations.git synced 2025-11-23 22:05:15 +02:00
Code Issues Releases Activity

Update README_ENG.md

Browse Source
This commit is contained in:
Anton Titovets
2025-11-21 10:34:24 +03:00
committed by GitHub
parent d258321d0f
commit 2316018b58
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README_ENG.md
View File

@@ -8,12 +8,11 @@
[![OneScript](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/Bayselonarrend/OpenIntegrations/refs/heads/main/media/os-logo.json)](https://github.com/EvilBeaver/OneScript)
[![Boosty](media/boosty.svg)](https://boosty.to/bayselonarrend)
<br>
A set of integration tools with popular APIs: console application (Windows/Linux) and library (extension) for 1C:Enterprise/OneScript, consisting of a common set of ready-made functions for working with multiple well-known cloud services <br>
**OpenIntegrations** is a set of tools for working with external APIs, available as a library (extension) for 1C:Enterprise / OneScript and a cross-platform console application for Windows and Linux. The project provides ready-made methods for performing application tasks (sending messages, creating documents, SQL queries, etc.) across more than 30 services and technologies, including Telegram, VK, Bitrix24, Google and Yandex services, as well as various DBMS and exchange protocols.
<br>
All implemented methods from the set perform specific application tasks, such as `SendMessage` or `CreatePost`, allowing them to be used without deep diving into the implementation. However, the code is well-decomposed: authorization methods, data retrieval, etc., are separated into distinct functions where possible. This facilitates easy addition of new methods based on existing ones without unraveling the implementation chain from the very beginning of API interaction <br><br>
The project code is organized as a set of independent modules, each responsible for working with a specific service. Common logic, such as HTTP or JSON handling, is extracted into reusable components. This allows for both quick application of ready-made functions and easy extension of functionality by adding new methods based on existing components. The source code is open, providing full control over implementation and enabling community participation in development. <br><br>
📋 Currently implemented methods for working with the following services ([list](/media/catalogs/Catalog.md))
<br>