@winible/winible-typed 2.51.1 → 2.51.3

package/README.md

@@ -1,104 +1,104 @@
-# Winible Typescript Models
-
-The Winible Typescript Models or `@winible/winible-typed` npm package is a project that holds all of Winible's sequelize database model declarations, sequelize client instantiation, as well as type declarations for unifying type sharing between all of our projects.
-
-## Overview
-
-This package serves as the central source of truth for Winible's database models and TypeScript types. It's used across multiple projects including:
-
-- Main backend
-- Lambda functions
-- Other Winible services
-
-## Installation
-
-```bash
-npm install @winible/winible-typed
-```
-
-## Project Structure
-
-```
-├── src/                    # Source code
-│   ├── types.ts           # Index types (NOT IN USE)
-│   ├── index.ts           # Main entry point
-│   └── recurlyInstance.ts # Recurly integration
-├── migrations/            # Database migrations (NOT IN USE)
-├── typed-model/          # Typed model definitions
-├── support/              # Support utilities (NOT IN USE)
-└── webhooks/            # Webhook handlers (NOT IN USE)
-```
-
-## Features
-
-- Sequelize model declarations
-- TypeScript type definitions
-- Database migrations (Not in use)
-- Shared database client instance
-
-## Development Setup
-
-1. Clone the repository:
-
-```bash
-git clone https://github.com/winible-betting/winible-typescript-models.git
-```
-
-2. Install dependencies:
-
-```bash
-npm install
-```
-
-3. Build the project:
-
-```bash
-npm run build
-```
-
-## Database Migrations
-
-While this package includes migration files in the `migrations/` directory, these migrations are currently not in use and should not be used. The migration system has been deprecated in favor of other database management approaches.
-
-## Contributing
-
-We use npm and [semantic versioning](#semantic-versioning) for making changes to the models and sharing. We need to be extremely careful when making major changes because almost all of winible's project use the npm package and are reliant on its typescript or model declarations, some of them use the sequelize instance to make database calls, like the [main backend](https://github.com/winible-betting/winible-backend) or some of our [lambda functions](https://github.com/winible-betting/winible-lambda-functions).
-
-### Releasing a new version
-
-1. Make the changes to the models needed
-2. PR your changes into main
-   1. Get approvals
-3. Merge into main
-4. Release a new version:
-   1. `npm version minor|major|patch` ← please refer to the [semantic versioning section](#semantic-versioning) for explanation
-      1. Most changes fall into a MINOR version category change (eg. updates to a existing data model, adding a new data model)
-   2. Run `npm run publish`. Note: you will get an error but that's normal, you can ignore it.
-5. Push new version change to main
-6. Update the Database manually
-7. Update the package version on all needed repositories by:
-   1. Manually changing the version on `package.json`
-   2. Using `npm run winible`
-      1. This will install the latest version of the package that being major, minor or patch
-
-### NPM Tags
-
-For more complex feature development that will require testing or major overhauls, we can use npm tag releases. Please follow the guide below:
-
-[How to Use NPM Tags](https://dev.to/andywer/how-to-use-npm-tags-4lla)
-
-After all testing is done and it's ready to release, make a [regular release](#releasing-a-new-version) with all the changes.
-
-## Misc
-
-### Links
-
-- [NPM Package](https://www.npmjs.com/package/@winible/winible-typed)
-
-### Semantic Versioning
-
-Given a version number MAJOR.MINOR.PATCH, we increment the:
-
-1. MAJOR version when you make incompatible API changes (1.x.x)
-2. MINOR version when you add functionality in a backward compatible manner (x.1.x)
-3. PATCH version when you make backward compatible bug fixes (x.x.1)
+# Winible Typescript Models
+
+The Winible Typescript Models or `@winible/winible-typed` npm package is a project that holds all of Winible's sequelize database model declarations, sequelize client instantiation, as well as type declarations for unifying type sharing between all of our projects.
+
+## Overview
+
+This package serves as the central source of truth for Winible's database models and TypeScript types. It's used across multiple projects including:
+
+- Main backend
+- Lambda functions
+- Other Winible services
+
+## Installation
+
+```bash
+npm install @winible/winible-typed
+```
+
+## Project Structure
+
+```
+├── src/                    # Source code
+│   ├── types.ts           # Index types (NOT IN USE)
+│   ├── index.ts           # Main entry point
+│   └── recurlyInstance.ts # Recurly integration
+├── migrations/            # Database migrations (NOT IN USE)
+├── typed-model/          # Typed model definitions
+├── support/              # Support utilities (NOT IN USE)
+└── webhooks/            # Webhook handlers (NOT IN USE)
+```
+
+## Features
+
+- Sequelize model declarations
+- TypeScript type definitions
+- Database migrations (Not in use)
+- Shared database client instance
+
+## Development Setup
+
+1. Clone the repository:
+
+```bash
+git clone https://github.com/winible-betting/winible-typescript-models.git
+```
+
+2. Install dependencies:
+
+```bash
+npm install
+```
+
+3. Build the project:
+
+```bash
+npm run build
+```
+
+## Database Migrations
+
+While this package includes migration files in the `migrations/` directory, these migrations are currently not in use and should not be used. The migration system has been deprecated in favor of other database management approaches.
+
+## Contributing
+
+We use npm and [semantic versioning](#semantic-versioning) for making changes to the models and sharing. We need to be extremely careful when making major changes because almost all of winible's project use the npm package and are reliant on its typescript or model declarations, some of them use the sequelize instance to make database calls, like the [main backend](https://github.com/winible-betting/winible-backend) or some of our [lambda functions](https://github.com/winible-betting/winible-lambda-functions).
+
+### Releasing a new version
+
+1. Make the changes to the models needed
+2. PR your changes into main
+   1. Get approvals
+3. Merge into main
+4. Release a new version:
+   1. `npm version minor|major|patch` ← please refer to the [semantic versioning section](#semantic-versioning) for explanation
+      1. Most changes fall into a MINOR version category change (eg. updates to a existing data model, adding a new data model)
+   2. Run `npm run publish`. Note: you will get an error but that's normal, you can ignore it.
+5. Push new version change to main
+6. Update the Database manually
+7. Update the package version on all needed repositories by:
+   1. Manually changing the version on `package.json`
+   2. Using `npm run winible`
+      1. This will install the latest version of the package that being major, minor or patch
+
+### NPM Tags
+
+For more complex feature development that will require testing or major overhauls, we can use npm tag releases. Please follow the guide below:
+
+[How to Use NPM Tags](https://dev.to/andywer/how-to-use-npm-tags-4lla)
+
+After all testing is done and it's ready to release, make a [regular release](#releasing-a-new-version) with all the changes.
+
+## Misc
+
+### Links
+
+- [NPM Package](https://www.npmjs.com/package/@winible/winible-typed)
+
+### Semantic Versioning
+
+Given a version number MAJOR.MINOR.PATCH, we increment the:
+
+1. MAJOR version when you make incompatible API changes (1.x.x)
+2. MINOR version when you add functionality in a backward compatible manner (x.1.x)
+3. PATCH version when you make backward compatible bug fixes (x.x.1)

package/dist/index.js

@@ -1,20 +1,20 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __exportStar = (this && this.__exportStar) || function(m, exports) {
-    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-__exportStar(require("./typed-model"), exports);
-__exportStar(require("./support"), exports);
-__exportStar(require("./src"), exports);
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+__exportStar(require("./typed-model"), exports);
+__exportStar(require("./support"), exports);
+__exportStar(require("./src"), exports);
 //# sourceMappingURL=index.js.map