@decaf-ts/for-http 0.2.11 → 0.2.13

package/LICENSE.md

@@ -20,56 +20,3 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
----
-
-## Section 2. AGPL Trigger: AI-Generated Code Usage
-
-If this software is incorporated into a product, service, or system that **uses AI generation of code**, then instead of MIT, the software is governed by the **GNU Affero General Public License v3.0 (AGPL-3.0)**, *in full*.
-
-**What “Uses AI generation of code” means (any of the following):**  
-1. The product uses AI to automatically generate **Decaf-TS front-end or back-end code**.  
-2. The product incorporates AI tools, pipelines, or workflows where **Decaf-TS code is generated** automatically or on demand.  
-3. Usage via **Decaf MCP** or any equivalent integration which enables AI-driven Decaf-TS code generation.  
-4. The product uses **Decaf-TS to dynamically generate UI** for AI agent conversation systems (chat, multimodal, interactive).  
-5. The product uses this software plus AI to generate software **“at scale”** (e.g. via automated bulk pipelines, continuous generation).  
-6. The product or service commercializes or sells software, tools, or applications **that were generated by AI using this software**.
-
-**Clarifications & Exceptions (these do *not* trigger AGPL):**  
-- If AI is used only during **development time** (e.g. a developer uses AI + Decaf tooling as an assistant, writes or reviews code, then commits)—this **does not** count as “uses AI generation of code” in Section 2.  
-- If a company builds a **Decaf-based product** using AI internally, but the **resulting product does not itself dynamically generate additional Decaf code**, then Section 2 is **not triggered**.  
-- If a company builds a **Decaf-based product** using AI internally, and while the **resulting product does generate it's UI dynamically via Decaf, the product does not itself dynamically generate additional Decaf code as a service**, then Section 2 is **not triggered**.
-
-In all other cases meeting the six trigger conditions above, the software is subject to AGPL-3.0 — you must comply with all AGPL obligations (source disclosure, network interaction clause, etc.)
-
-## Section 3. Reference to AGPL
-
-The full text of the GNU Affero General Public License v3.0 is available from the Free Software Foundation at:  
-https://www.gnu.org/licenses/agpl-3.0.html
-
----
-
-## Notes & Examples (for clarity)
-
-- A CLI tool that helps you scaffold Decaf code locally (without runtime AI generation) remains under MIT.  
-- A web service that uses AI at runtime to produce new Decaf UI or backend code for users must operate under AGPL.  
-- A SaaS product that sells modules generated via AI using this software falls under AGPL.  
-- Internal use or development with AI suggestions, without dynamic generation in the delivered product, is under MIT.
-
----
-
-**Legal disclaimers, warranty, and liability** follow the same as in MIT or AGPL as applicable.  
-
----
-
-### Why this is more “bullet-proof” (improvements over earlier drafts)
-
-- The **trigger conditions** are enumerated and explicit (six bullet points).  
-- The **exceptions** are limited and clearly stated (development-time, non-code-generating product).  
-- We embed the MIT text fully (so recipients see their rights).  
-- We **link to the full AGPL** rather than embed it (keeping the file manageable) but still make it binding by reference.  
-- We include a **Notes & Examples** section to show boundary cases and reduce ambiguity.  
-- The style is more “plain English + structured” (like n8n’s) to reduce misinterpretation.  
-
----
-
-If you like, I can generate this as a **downloadable `LICENSE.md` file** for you right away, so you can drop it in your repo. Would you like me to do that?

package/README.md

@@ -1,10 +1,9 @@
-![Banner](./assets/Banner.png)
+![Banner](./workdocs/assets/decaf-logo.svg)
 
 # decaf-ts/for-http
 
 A lightweight HTTP adapter layer for decaf-ts that enables CRUD-style repositories and services over REST APIs. It defines a generic HttpAdapter with concrete implementations (e.g., Axios), a RestService for simple model-centric operations, and a RestRepository when you need repository decoration logic before submitting to the backend. Includes minimal types for configuration and request flags.
 
-
 ![Licence](https://img.shields.io/github/license/decaf-ts/for-http.svg?style=plastic)
 ![GitHub language count](https://img.shields.io/github/languages/count/decaf-ts/for-http?style=plastic)
 ![GitHub top language](https://img.shields.io/github/languages/top/decaf-ts/for-http?style=plastic)
@@ -28,6 +27,9 @@ A lightweight HTTP adapter layer for decaf-ts that enables CRUD-style repositori
 
 Documentation available [here](https://decaf-ts.github.io/for-http/)
 
+Minimal size: 1.7 KB kb gzipped
+
+
 # decaf-ts/for-http — Detailed Description
 
 This package provides a small, focused HTTP integration for decaf-ts. It introduces a generic HttpAdapter abstraction that maps REST semantics (create/read/update/delete and bulk variants) onto decaf-ts repositories and services, plus minimal configuration and flags. A ready-to-use Axios adapter is included.
@@ -305,6 +307,24 @@ const f: AxiosFlags = { headers: { "X-Trace": "1" } };
 ```
 
 
+## Coding Principles
+
+- group similar functionality in folders (analog to namespaces but without any namespace declaration)
+- one class per file;
+- one interface per file (unless interface is just used as a type);
+- group types as other interfaces in a types.ts file per folder;
+- group constants or enums in a constants.ts file per folder;
+- group decorators in a decorators.ts file per folder;
+- always import from the specific file, never from a folder or index file (exceptions for dependencies on other packages);
+- prefer the usage of established design patters where applicable:
+  - Singleton (can be an anti-pattern. use with care);
+  - factory;
+  - observer;
+  - strategy;
+  - builder;
+  - etc;
+
+
 ### Related
 
 [![decaf-ts](https://github-readme-stats.vercel.app/api/pin/?username=decaf-ts&repo=decaf-ts)](https://github.com/decaf-ts/decaf-ts)
@@ -345,6 +365,6 @@ So if you can, if this project in any way. either by learning something or simpl
 
 ## License
 
-This project is released under MIT with an AGPL-3.0 trigger for AI-generated code usage; MIT covers standard development, but AI-driven Decaf code generation activates full AGPL obligations—see [LICENSE.md](./LICENSE.md) for full terms.
+This project is released under the [MIT License](./LICENSE.md).
 
 By developers, for developers...