stabilize-orm 1.3.8 → 2.1.0

package/CHANGELOG.md

@@ -1,75 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-## [Unreleased]
-
-- Further features and improvements coming soon.
-
-
-## [1.3.2] - 2025-10-19
-
-### Added
-- Added **Timestamps Configuration** feature for automatic management of `createdAt` and `updatedAt` columns (`types.ts`, `model.ts`, `repository.ts`, `migrations.ts`).
-  - Added `TimestampsConfig` interface and `timestamps` property to `ModelConfig` in `types.ts`.
-  - Added `getTimestamps` method to `MetadataStorage` in `model.ts`.
-  - Updated `create`, `update`, `bulkCreate`, `bulkUpdate`, and `upsert` methods in `repository.ts` to set timestamps automatically.
-  - Updated `migrations.ts` to include timestamp columns in schema generation.
-  - Updated `README.md` with a new "Timestamps" section and example.
-
-### Fixed
-- Fixed TypeScript error (TS7053) in `repository.ts` for timestamps handling in `_create`, `_bulkCreate`, `_bulkUpdate`, and `_upsert` methods by using `Record<string, any>` for safe property access and maintaining `Partial<T>` type safety.
-
-## [1.3.2] - 2025-10-19
-
-### Added
-- Added **Custom Query Scopes** feature, allowing reusable query conditions defined in model configurations (`types.ts`, `model.ts`, `query-builder.ts`, `repository.ts`).
-  - Added `scopes` property to `ModelConfig` interface in `types.ts` to define scope functions.
-  - Added `getScopes` method to `MetadataStorage` in `model.ts` to retrieve scope definitions.
-  - Added `scope` method to `QueryBuilder` in `query-builder.ts` to apply scopes to queries.
-  - Added `scope` method to `Repository` in `repository.ts` for direct scope application.
-  - Updated `README.md` with a new "Custom Query Scopes" section and example.
-
-## [1.3.0] - 2025-10-18
-
-### Added
-- Introduced programmatic `defineModel` API for model definitions, eliminating the need for decorators (`model.ts`).
-- Added `MetadataStorage` class to manage model configurations without `reflect-metadata`.
-- Added support for defining lifecycle hooks in `ModelConfig` or as class methods (`hooks.ts`).
-- Added `example.ts` to demonstrate the new programmatic API usage.
-- Extended `ModelConfig` interface to support columns, relations, hooks, versioning, and soft deletes (`types.ts`).
-
-### Changed
-- Replaced decorator-based model definitions with `defineModel` API, removing dependency on `reflect-metadata` and TypeScript experimental features (`experimentalDecorators`, `emitDecoratorMetadata`).
-- Updated `stabilize.ts` to export `defineModel` and remove `reflect-metadata` import.
-- Modified `repository.ts` to use `MetadataStorage` for table names, columns, relations, validators, and soft delete fields.
-- Rewrote `hooks.ts` to support hooks via `ModelConfig` and class methods, integrated with `MetadataStorage`.
-- Updated `migrations.ts` to generate schemas using `MetadataStorage` instead of decorator metadata.
-- Revised `types.ts` to remove decorator-related types and add `ModelConfig`, `ColumnConfig`, and `RelationConfig` interfaces.
-- Updated `README.md` to reflect the new programmatic API, remove decorator references, and update examples.
-- Ensured compatibility with `verbatimModuleSyntax` by using `export type` for type exports in `stabilize.ts`.
-
-### Removed
-- Deleted `decorators.ts` as decorators are no longer used.
-- Removed dependency on `reflect-metadata` from the project.
-
-### Fixed
-- Fixed TypeScript type errors in `repository.ts` for `columns` and `relations` by mapping `MetadataStorage` outputs to match expected types.
-- Corrected `runHooks` in `repository.ts` to call `hook.callback(entity)` instead of `hook()`.
-- Fixed TypeScript `verbatimModuleSyntax` error in `stabilize.ts` by separating type and value exports.
-
-## [1.1.2] - 2025-10-14
-
-### Added
-- Improved repository QueryBuilder with chainable joins, advanced where clauses, and cache support.
-- Added support for model decorators and repository pattern.
-- New CLI features for migrations, seeds, rollback, and status.
-- Security, funding, conduct, and contributing markdowns.
-- More expressive README and docs.
-
-### Changed
-- Updated ORM configuration examples.
-- Enhanced documentation for open source best practices.
-
-### Fixed
-- Various bug fixes for connection handling and retry logic.

package/CODE_OF_CONDUCT.md

@@ -1,87 +0,0 @@
-# 📝 Contributor Covenant Code of Conduct
-
-## 💚 Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
----
-
-## 🌟 Our Standards
-
-**Positive behaviors include:**
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall community
-
-**Unacceptable behaviors include:**
-- The use of sexualized language or imagery, and sexual attention or advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others’ private information, such as a physical or email address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
----
-
-## 🛡️ Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
-
----
-
-## 🌍 Scope
-
-This Code of Conduct applies within all community spaces and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
----
-
-## 📣 Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **lwazicd@icloud.com**.
-
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
----
-
-## ⚖️ Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-- **Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-- **Consequence:** A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. May include a public apology.
-
-### 2. Warning
-
-- **Community Impact:** A violation through a single incident or series of actions.
-- **Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-- **Community Impact:** A serious violation of community standards, including sustained inappropriate behavior.
-- **Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-- **Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-- **Consequence:** A permanent ban from any sort of public interaction within the community.
-
----
-
-## 📜 Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at  
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
-
-For answers to common questions about this code of conduct, see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).  
-Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
-
----

package/CONTRIBUTING.md

@@ -1,48 +0,0 @@
-# 🤝 Contributing to Stabilize ORM
-
-Thank you for your interest in making Stabilize ORM even better! Your ideas, code, and feedback help drive this project forward.
-
----
-
-## 🚀 How to Contribute
-
-1. **Fork the Repository:**  
-   Click "Fork" to make your own copy.
-2. **Create Your Branch:**  
-   Branch off `main` for your feature or fix.
-3. **Write Code:**  
-   - Use TypeScript.
-   - Follow established formatting and naming conventions.
-4. **Test Your Changes:**  
-   Ensure your code passes all tests.
-5. **Update Documentation:**  
-   If you change APIs, update the docs and README.
-6. **Open a Pull Request:**  
-   - Fill out the PR template.
-   - Describe your changes clearly.
-
----
-
-## 💡 Code Style
-
-- **Language:** TypeScript only
-- **Formatting:** Use project conventions (Prettier, ESLint, etc.)
-- **Naming:** Be descriptive and consistent
-
----
-
-## 🐞 Reporting Issues
-
-- For bugs, use the [Bug Report Issue Template](.github/ISSUE_TEMPLATE/bug_report.md).
-- For feature ideas, use the [Feature Request Template](.github/ISSUE_TEMPLATE/feature_request.md).
-
-If in doubt, ask or open a discussion!
-
----
-
-## 🙏 Thank You
-
-Your contributions make Stabilize ORM stable, expressive, and truly open source.  
-Happy coding!
-
----

package/FUNDING.md

@@ -1,14 +0,0 @@
-# ❤️ Support Stabilize ORM
-
-If you love Stabilize ORM and want to help it grow, you can support ongoing development in a few ways:
-
-- **GitHub Sponsors:**  
-  [Sponsor ElectronSz on GitHub](https://github.com/sponsors/ElectronSz)
-
-- **Patreon:**  
-  [Become a Patron](https://patreon.com/ElectronSz)
-
-- **Ko-fi:**  
-  [Buy ElectronSz a coffee](https://ko-fi.com/ElectronSz)
-
-Your support helps with maintenance, new features, and keeping Stabilize ORM open source for everyone. Thank you! 🙏

package/SECURITY.md

@@ -1,35 +0,0 @@
-# 🛡️ Security Policy
-
-## Supported Versions
-
-We encourage responsible disclosure of security vulnerabilities for all actively maintained versions of Stabilize ORM.
-
-| Version      | Supported         |
-|--------------|------------------|
-| Latest (main)| ✅ Yes            |
-| Older (< 6mo)| ✅ Yes            |
-| Unmaintained | ❌ No             |
-
-## Reporting a Vulnerability
-
-If you discover a security vulnerability, please **do not disclose it publicly**.
-
-### Secure Reporting Steps
-
-1. **Email:**  
-   Contact ElectronSz directly at [lwazicd@icloud.com](mailto:lwazicd@icloud.com) with full details.
-
-2. **GitHub Security Advisory:**  
-   Alternatively, open a [GitHub security advisory](https://github.com/ElectronSz/stabilize-orm/security/advisories) (private by default).
-
-3. **Wait for Response:**  
-   Please allow up to 72 hours for a first response. We may request more details or verification.
-
-4. **Coordinated Disclosure:**  
-   We will work with you to verify, patch, and coordinate public disclosure.
-
----
-
-> **Please do NOT post vulnerabilities in GitHub issues, discussions, or any public forum until a fix is released.**
-
-Thank you for helping keep Stabilize ORM and its users safe!

package/SUPPORT.md

@@ -1,18 +0,0 @@
-# 🤝 Support
-
-Need help with Stabilize ORM? We're here for you!
-
-## 📬 How to Get Support
-
-- **Open an Issue:**  
-  Have a bug, question, or need help? [Create an issue on GitHub](https://github.com/ElectronSz/stabilize-orm/issues) and our community will assist you.
-
-- **Security Concerns:**  
-  If you’ve found a security vulnerability, please see our [Security Policy](SECURITY.md) for private and responsible reporting.
-
-## 💬 Community
-
-- Join discussions, share feedback, and connect with other users and contributors.
-- Contributions, suggestions, and PRs are always welcome!
-
-Thank you for using Stabilize ORM!