liminal-orm 1.0.3.dev1__tar.gz → 1.0.4__tar.gz

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/PKG-INFO

@@ -1,7 +1,8 @@
 Metadata-Version: 2.1
 Name: liminal-orm
-Version: 1.0.3.dev1
+Version: 1.0.4
 Summary: An ORM and toolkit that builds on top of Benchling's platform to keep your schemas and downstream code dependencies in sync.
+Home-page: https://github.com/dynotx/liminal-orm
 Author: DynoTx Open Source
 Author-email: opensource@dynotx.com
 Requires-Python: >=3.9,<4
@@ -19,26 +20,30 @@ Requires-Dist: rich (>=13.9.2,<14.0.0)
 Requires-Dist: sqlalchemy (<2)
 Requires-Dist: tenacity (>=8,<10)
 Requires-Dist: typer (>=0.12.5,<0.13.0)
+Project-URL: Bug Tracker, https://github.com/dynotx/liminal-orm/issues
+Project-URL: Documentation, https://dynotx.github.io/liminal-orm/
+Project-URL: Repository, https://github.com/dynotx/liminal-orm
 Description-Content-Type: text/markdown
 
 # [Liminal ORM](#liminal-orm)
 
-Liminal ORM<sup>1</sup> is a Python package that builds on top of [Benchling](https://www.benchling.com/)'s LIMS<sup>2</sup> platform to keep your Benchling schemas and downstream code dependencies in sync. Liminal provides an ORM framework using [SQLAlchemy](https://github.com/sqlalchemy/sqlalchemy) that allows you to define all your Benchling schemas in code. This creates a single source of truth that Benchling managers can use to keep multiple tenants in sync. This enables a code-first approach for managing Benchling tenants and accessing Benchling data. With the schemas defined in code, you can now take advantage of the additional capabilities that the Liminal toolkit provides. This includes:
+Liminal ORM<sup>1</sup> is an open-source Python package that builds on [Benchling's](https://www.benchling.com/) LIMS<sup>2</sup> platform and provides a simple framework to keep your upstream Benchling schemas and downstream dependencies in sync. Liminal provides an ORM framework using [SQLAlchemy](https://github.com/sqlalchemy/sqlalchemy) along with a schema migration service inspired by [Alembic](https://alembic.sqlalchemy.org/en/latest/). This allows you to define your Benchling schemas in code and create a *single source of truth* that synchronizes with your upstream Benchling tenant(s) and downstream dependencies. Through one line CLI commands, Liminal enables a code-first approach for managing Benchling tenants and accessing Benchling data. With the schemas defined in code, you can also take advantage of the additional capabilities that the Liminal toolkit provides. This includes:
 
-- The ability to run migrations to your Benchling tenant(s) through an easy to use CLI<sup>3</sup>.
+- The ability to run migrations to your Benchling tenant(s) through an easy to use CLI.
 - One source of truth defined in code for your Benchling schema model that your many Benchling tenants can stay in sync with.
 - Easy to implement validation rules to reflect business logic for all of your Benchling entities.
 - Strongly typed queries for all your Benchling entities.
 - CI/CD integration with GitHub Actions to ensure that your Benchling schemas and code are always in sync.
-- And more!
+- And more based on community contributions/feedback :)
 
 Benchling is an industry standard cloud platform for life sciences R&D. Liminal builds on top of Benchling's platform and assumes that you already have a Benchling tenant set up and have (or have access to) an admin user account. If not, learn more about getting started with Benchling [here](https://www.benchling.com/explore-benchling)!
 
-For a full and in-depth overview of Liminal, please refer to our [full documentation](https://dynotx.github.io/liminal-orm/). Below is a [quickstart guide](#getting-started) to get you Liminal set up in your project.
+If you are a Benchling user, try out Liminal by following the [quickstart guide](./getting-started/prerequisites.md)! Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions) forum with any questions or to simply introduce yourself! If there is something blocking you from using Liminal or you're having trouble setting Liminal up, please share in [Issues](https://github.com/dynotx/liminal-orm/issues) or reach out directly (contact information below). You can expect responses within 48 hours :)
 
-Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions) forum with any questions or to simply introduce yourself! If you run into any issues, during setup or usage, don't hesitate to post in [Issues](https://github.com/dynotx/liminal-orm/issues) or reach out directly at <opensource@dynotx.com>. You can expect responses within 48 hours :) 
+Nirmit Damania is the creator and current maintainer of Liminal (I post Liminal updates to [Discussions](https://github.com/dynotx/liminal-orm/discussions) and my [LinkedIn](https://www.linkedin.com/in/nirmit-damania/)). Most importantly, **you** have the ability to influence the future of Liminal! Any feedback, positive or negative, is highly encouraged and will be used to steer the direction of Liminal. Refer to the [Contributing guide](https://github.com/dynotx/liminal-orm/blob/main/CONTRIBUTING.md) to learn more about how you can contribute to Liminal.
 
 ⭐️ Leave a star on the repo to spread the word!
+If you or your organization use Liminal, please consider adding yourself or your organization to the [Users](https://github.com/dynotx/liminal-orm/blob/main/USERS.md) list.
 
 <img width="793" alt="liminal_simple_graph" src="https://github.com/user-attachments/assets/52e32cd0-3407-49f5-b100-5763bee3830c">
 
@@ -50,6 +55,7 @@ Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions
   - [Setup](#setup)
   - [Migration](#migration)
   - [Toolkit](#toolkit)
+- [Mission](#mission)
 - [Community](#community)
 - [Contributing](#contributing)
 - [License](#license)
@@ -141,18 +147,22 @@ With your schemas defined in code, you can now take advantage of the additional
 1. Entity validation: Easily create custom validation rules for your Benchling entities.
 
     ```python
-    from dyno.liminal.orm.base_model import BaseModel
-    from dyno.liminal.orm.mixins import CustomEntityMixin
-
-    class Pizza(BaseModel, CustomEntityMixin):
-        ...
-
-        @validator(BenchlingReportLevel.HIGH)
-        def cook_temp_time(self):
-            if self.cook_time is not None and self.cook_temp is None:
-                raise ValueError("Cook temp is required if cook time is set")
-            if self.cook_time is None and self.cook_temp is not None:
-                raise ValueError("Cook time is required if cook temp is set")
+    from liminal.validation import BenchlingValidator, BenchlingValidatorReport, BenchlingReportLevel
+    from liminal.orm.base_model import BaseModel
+
+    class CookTempValidator(BenchlingValidator):
+        """Validates that a field value is a valid enum value for a Benchling entity"""
+
+        def validate(self, entity: type[BaseModel]) -> BenchlingValidatorReport:
+            valid = True
+            message = None
+            if entity.cook_time is not None and entity.cook_temp is None:
+                valid = False
+                message = "Cook temp is required if cook time is set"
+            if entity.cook_time is None and entity.cook_temp is not None:
+                valid = False
+                message = "Cook time is required if cook temp is set"
+            return self.create_report(valid, BenchlingReportLevel.MED, entity, message)
     ```
 
 2. Strongly typed queries: Write type-safe queries using SQLAlchemy to access your Benchling entities.
@@ -167,6 +177,10 @@ With your schemas defined in code, you can now take advantage of the additional
 
 4. And more to come!
 
+## [Mission](#mission)
+
+The democratization of software in Biotech is crucial. By building a community around complex, yet common, problems and creating open-source solutions, we can work together to tackle these challenges together and enable faster innovation in the industry. By breaking down the silos between private platforms, we can enable a more dynamic and open ecosystem. This was the motivation for Liminal's creation. Liminal's goal is to create an open-source software product that enables a standard, code-first approach to configuration and change management for LIMS systems. We started with Benchling, but the goal is to make Liminal the go-to solution for any LIMS system.
+
 ## [Community](#community)
 
 We're excited to hear from you! Feel free to introduce yourself on the [Liminal GitHub Discussions page](https://github.com/dynotx/liminal-orm/discussions/categories/intros)
@@ -184,6 +198,11 @@ Please refer to [CONTRIBUTING.md](./CONTRIBUTING.md) to learn how to contribute
 
 Liminal ORM is distributed under the [Apache License, Version 2.0](./LICENSE.md).
 
+## [Direct Contact](#direct-contact)
+
+- Email: <opensource@dynotx.com>
+- LinkedIn: [Nirmit Damania](https://www.linkedin.com/in/nirmit-damania/)
+
 ## [Acknowledgements](#acknowledgements)
 
 This project could not have been started without the support of Dyno Therapeutics and the help of the following people.

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/README.md

@@ -1,21 +1,22 @@
 # [Liminal ORM](#liminal-orm)
 
-Liminal ORM<sup>1</sup> is a Python package that builds on top of [Benchling](https://www.benchling.com/)'s LIMS<sup>2</sup> platform to keep your Benchling schemas and downstream code dependencies in sync. Liminal provides an ORM framework using [SQLAlchemy](https://github.com/sqlalchemy/sqlalchemy) that allows you to define all your Benchling schemas in code. This creates a single source of truth that Benchling managers can use to keep multiple tenants in sync. This enables a code-first approach for managing Benchling tenants and accessing Benchling data. With the schemas defined in code, you can now take advantage of the additional capabilities that the Liminal toolkit provides. This includes:
+Liminal ORM<sup>1</sup> is an open-source Python package that builds on [Benchling's](https://www.benchling.com/) LIMS<sup>2</sup> platform and provides a simple framework to keep your upstream Benchling schemas and downstream dependencies in sync. Liminal provides an ORM framework using [SQLAlchemy](https://github.com/sqlalchemy/sqlalchemy) along with a schema migration service inspired by [Alembic](https://alembic.sqlalchemy.org/en/latest/). This allows you to define your Benchling schemas in code and create a *single source of truth* that synchronizes with your upstream Benchling tenant(s) and downstream dependencies. Through one line CLI commands, Liminal enables a code-first approach for managing Benchling tenants and accessing Benchling data. With the schemas defined in code, you can also take advantage of the additional capabilities that the Liminal toolkit provides. This includes:
 
-- The ability to run migrations to your Benchling tenant(s) through an easy to use CLI<sup>3</sup>.
+- The ability to run migrations to your Benchling tenant(s) through an easy to use CLI.
 - One source of truth defined in code for your Benchling schema model that your many Benchling tenants can stay in sync with.
 - Easy to implement validation rules to reflect business logic for all of your Benchling entities.
 - Strongly typed queries for all your Benchling entities.
 - CI/CD integration with GitHub Actions to ensure that your Benchling schemas and code are always in sync.
-- And more!
+- And more based on community contributions/feedback :)
 
 Benchling is an industry standard cloud platform for life sciences R&D. Liminal builds on top of Benchling's platform and assumes that you already have a Benchling tenant set up and have (or have access to) an admin user account. If not, learn more about getting started with Benchling [here](https://www.benchling.com/explore-benchling)!
 
-For a full and in-depth overview of Liminal, please refer to our [full documentation](https://dynotx.github.io/liminal-orm/). Below is a [quickstart guide](#getting-started) to get you Liminal set up in your project.
+If you are a Benchling user, try out Liminal by following the [quickstart guide](./getting-started/prerequisites.md)! Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions) forum with any questions or to simply introduce yourself! If there is something blocking you from using Liminal or you're having trouble setting Liminal up, please share in [Issues](https://github.com/dynotx/liminal-orm/issues) or reach out directly (contact information below). You can expect responses within 48 hours :)
 
-Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions) forum with any questions or to simply introduce yourself! If you run into any issues, during setup or usage, don't hesitate to post in [Issues](https://github.com/dynotx/liminal-orm/issues) or reach out directly at <opensource@dynotx.com>. You can expect responses within 48 hours :) 
+Nirmit Damania is the creator and current maintainer of Liminal (I post Liminal updates to [Discussions](https://github.com/dynotx/liminal-orm/discussions) and my [LinkedIn](https://www.linkedin.com/in/nirmit-damania/)). Most importantly, **you** have the ability to influence the future of Liminal! Any feedback, positive or negative, is highly encouraged and will be used to steer the direction of Liminal. Refer to the [Contributing guide](https://github.com/dynotx/liminal-orm/blob/main/CONTRIBUTING.md) to learn more about how you can contribute to Liminal.
 
 ⭐️ Leave a star on the repo to spread the word!
+If you or your organization use Liminal, please consider adding yourself or your organization to the [Users](https://github.com/dynotx/liminal-orm/blob/main/USERS.md) list.
 
 <img width="793" alt="liminal_simple_graph" src="https://github.com/user-attachments/assets/52e32cd0-3407-49f5-b100-5763bee3830c">
 
@@ -27,6 +28,7 @@ Reach out in the [Discussions](https://github.com/dynotx/liminal-orm/discussions
   - [Setup](#setup)
   - [Migration](#migration)
   - [Toolkit](#toolkit)
+- [Mission](#mission)
 - [Community](#community)
 - [Contributing](#contributing)
 - [License](#license)
@@ -118,18 +120,22 @@ With your schemas defined in code, you can now take advantage of the additional
 1. Entity validation: Easily create custom validation rules for your Benchling entities.
 
     ```python
-    from dyno.liminal.orm.base_model import BaseModel
-    from dyno.liminal.orm.mixins import CustomEntityMixin
-
-    class Pizza(BaseModel, CustomEntityMixin):
-        ...
-
-        @validator(BenchlingReportLevel.HIGH)
-        def cook_temp_time(self):
-            if self.cook_time is not None and self.cook_temp is None:
-                raise ValueError("Cook temp is required if cook time is set")
-            if self.cook_time is None and self.cook_temp is not None:
-                raise ValueError("Cook time is required if cook temp is set")
+    from liminal.validation import BenchlingValidator, BenchlingValidatorReport, BenchlingReportLevel
+    from liminal.orm.base_model import BaseModel
+
+    class CookTempValidator(BenchlingValidator):
+        """Validates that a field value is a valid enum value for a Benchling entity"""
+
+        def validate(self, entity: type[BaseModel]) -> BenchlingValidatorReport:
+            valid = True
+            message = None
+            if entity.cook_time is not None and entity.cook_temp is None:
+                valid = False
+                message = "Cook temp is required if cook time is set"
+            if entity.cook_time is None and entity.cook_temp is not None:
+                valid = False
+                message = "Cook time is required if cook temp is set"
+            return self.create_report(valid, BenchlingReportLevel.MED, entity, message)
     ```
 
 2. Strongly typed queries: Write type-safe queries using SQLAlchemy to access your Benchling entities.
@@ -144,6 +150,10 @@ With your schemas defined in code, you can now take advantage of the additional
 
 4. And more to come!
 
+## [Mission](#mission)
+
+The democratization of software in Biotech is crucial. By building a community around complex, yet common, problems and creating open-source solutions, we can work together to tackle these challenges together and enable faster innovation in the industry. By breaking down the silos between private platforms, we can enable a more dynamic and open ecosystem. This was the motivation for Liminal's creation. Liminal's goal is to create an open-source software product that enables a standard, code-first approach to configuration and change management for LIMS systems. We started with Benchling, but the goal is to make Liminal the go-to solution for any LIMS system.
+
 ## [Community](#community)
 
 We're excited to hear from you! Feel free to introduce yourself on the [Liminal GitHub Discussions page](https://github.com/dynotx/liminal-orm/discussions/categories/intros)
@@ -161,6 +171,11 @@ Please refer to [CONTRIBUTING.md](./CONTRIBUTING.md) to learn how to contribute
 
 Liminal ORM is distributed under the [Apache License, Version 2.0](./LICENSE.md).
 
+## [Direct Contact](#direct-contact)
+
+- Email: <opensource@dynotx.com>
+- LinkedIn: [Nirmit Damania](https://www.linkedin.com/in/nirmit-damania/)
+
 ## [Acknowledgements](#acknowledgements)
 
 This project could not have been started without the support of Dyno Therapeutics and the help of the following people.

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/base/base_dropdown.py

@@ -3,6 +3,16 @@ from typing import Any
 
 
 class BaseDropdown(ABC):
+    """_summary_
+
+    Parameters
+    ----------
+    __benchling_name__: str
+        The name of the dropdown in Benchling. There can be no duplicate dropdown names in Benchling.
+    __allowed_values__: list[str]
+        The list of values for the dropdown. Order matters and reflects the order of the dropdown in Benchling. Values must be unique.
+    """
+
     __benchling_name__: str
     __allowed_values__: list[str]
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/cli/cli.py

@@ -78,8 +78,8 @@ def generate_files(
     benchling_tenant: str = typer.Argument(
         ..., help="Benchling tenant (or alias) to connect to."
     ),
-    write_path: Path = typer.Argument(
-        ..., help="The path to write the generated files to."
+    write_path: Path = typer.Option(
+        Path("."), help="The path to write the generated files to."
     ),
 ) -> None:
     current_revision_id, benchling_connection = read_local_env_file(

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/connection/benchling_service.py

@@ -27,9 +27,9 @@ class BenchlingService(Benchling):
         The connection object that contains the credentials for the Benchling tenant.
     use_api: bool
         Whether to connect to the Benchling SDK. Requires api_client_id and api_client_secret from the connection object.
-    use_db: bool
+    use_db: bool = False
         Whether to connect to the Benchling Postgres database. Requires warehouse_connection_string from the connection object.
-    use_internal_api: bool
+    use_internal_api: bool = False
         Whether to connect to the Benchling internal API. Requires internal_api_admin_email and internal_api_admin_password from the connection object.
     """
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/dropdowns/compare.py

@@ -19,7 +19,7 @@ def compare_dropdowns(
 ) -> dict[str, list[CompareOperation]]:
     dropdown_operations: dict[str, list[CompareOperation]] = {}
     benchling_dropdowns: dict[str, Dropdown] = get_benchling_dropdowns_dict(
-        benchling_service
+        benchling_service, include_archived=True
     )
     processed_benchling_names = set()
     model_dropdowns = BaseDropdown.get_all_subclasses(dropdown_names)

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/dropdowns/utils.py

@@ -57,15 +57,15 @@ def get_benchling_dropdown_by_name(
 
 def get_benchling_dropdowns_dict(
     benchling_service: BenchlingService,
+    include_archived: bool = False,
 ) -> dict[str, Dropdown]:
-    with requests.Session() as session:
-        request = session.get(
-            f"https://{benchling_service.benchling_tenant}.benchling.com/1/api/schema-field-selectors/?registryId={benchling_service.registry_id}",
-            headers=benchling_service.custom_post_headers,
-            cookies=benchling_service.custom_post_cookies,
-        )
-    return {
-        d["name"]: Dropdown(
+    def _convert_dropdown_from_json(
+        d: dict[str, Any], include_archived: bool = False
+    ) -> Dropdown:
+        all_options = d["allSchemaFieldSelectorOptions"]
+        if not include_archived:
+            all_options = [o for o in all_options if not o["archiveRecord"]]
+        return Dropdown(
             id=d["id"],
             name=d["name"],
             archive_record=BenchlingArchiveRecord(reason=d["archiveRecord"]["purpose"])
@@ -81,11 +81,26 @@ def get_benchling_dropdowns_dict(
                     if o["archiveRecord"]
                     else None,
                 )
-                for o in d["allSchemaFieldSelectorOptions"]
+                for o in all_options
             ],
         )
-        for d in request.json()["selectorsByRegistryId"][benchling_service.registry_id]
+
+    with requests.Session() as session:
+        request = session.get(
+            f"https://{benchling_service.benchling_tenant}.benchling.com/1/api/schema-field-selectors/?registryId={benchling_service.registry_id}",
+            headers=benchling_service.custom_post_headers,
+            cookies=benchling_service.custom_post_cookies,
+        )
+        all_dropdowns = request.json()["selectorsByRegistryId"][
+            benchling_service.registry_id
+        ]
+        if not include_archived:
+            all_dropdowns = [d for d in all_dropdowns if not d["archiveRecord"]]
+    dropdowns = {
+        d["name"]: _convert_dropdown_from_json(d, include_archived)
+        for d in all_dropdowns
     }
+    return dropdowns
 
 
 def dropdown_exists_in_benchling(

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/entity_schemas/generate_files.py

@@ -90,7 +90,7 @@ def generate_all_entity_schema_files(
                 dropdown_classname = dropdown_name_to_classname_map[col.dropdown_link]
                 dropdowns.append(dropdown_classname)
             column_strings.append(
-                f"""{tab}{col_name}: SqlColumn = Column(name="{col.name}", type={str(col.type)}, required={col.required}{', is_multi=True' if col.is_multi else ''}{', parent_link=True' if col.parent_link else ''}{f', entity_link="{col.entity_link}"' if col.entity_link else ''}{f', dropdown={dropdown_classname}' if dropdown_classname else ''})"""
+                f"""{tab}{col_name}: SqlColumn = Column(name="{col.name}", type={str(col.type)}, required={col.required}{', is_multi=True' if col.is_multi else ''}{', parent_link=True' if col.parent_link else ''}{f', entity_link="{col.entity_link}"' if col.entity_link else ''}{f', dropdown={dropdown_classname}' if dropdown_classname else ''}{f', tooltip="{col.tooltip}"' if col.tooltip else ''})"""
             )
             if col.required and col.type:
                 init_strings.append(

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/entity_schemas/utils.py

@@ -41,6 +41,9 @@ def convert_tag_schema_to_internal_schema(
     dropdowns_map: dict[str, str],
     include_archived_fields: bool = False,
 ) -> tuple[SchemaProperties, dict[str, BaseFieldProperties]]:
+    all_fields = tag_schema.allFields
+    if not include_archived_fields:
+        all_fields = [f for f in all_fields if not f.archiveRecord]
     return (
         SchemaProperties(
             name=tag_schema.name,
@@ -63,11 +66,7 @@ def convert_tag_schema_to_internal_schema(
         ).set_archived(tag_schema.archiveRecord is not None),
         {
             f.systemName: convert_tag_schema_field_to_field_properties(f, dropdowns_map)
-            for f in (
-                tag_schema.allFields
-                if include_archived_fields
-                else [f for f in tag_schema.allFields if not f.archiveRecord]
-            )
+            for f in all_fields
         },
     )
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/migrate/revision.py

@@ -165,7 +165,7 @@ class Revision(BaseModel):
         Path
             The path to the revision file that was written.
         """
-        created_date = datetime.now().strftime("%Y-%m-%d %H:%M:%S.%f")
+        created_date = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
         upgrade_operation_strings = [
             o.revision_file_string() for o in self.upgrade_operations
         ]

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/migrate/utils.py

@@ -15,8 +15,9 @@ def _check_env_file(env_file_path: Path) -> None:
 def read_local_env_file(
     env_file_path: Path, benchling_tenant: str
 ) -> tuple[str, BenchlingConnection]:
-    """Imports the env.py file from the current working directory and returns the CURRENT_REVISION_ID variable.
+    """Imports the env.py file from the current working directory and returns the CURRENT_REVISION_ID variable along with the BenchlingConnection object.
     The env.py file is expected to have the CURRENT_REVISION_ID variable set to the revision id you are currently on.
+    The BenchlingConnection object is expected to be defined and have connection information for the Benchling API client and internal API.
     """
     _check_env_file(env_file_path)
     module_path = Path.cwd() / env_file_path
@@ -26,22 +27,34 @@ def read_local_env_file(
     module = importlib.util.module_from_spec(spec)
     spec.loader.exec_module(module)
     for attr_name in dir(module):
-        attr = getattr(module, attr_name)
-        if isinstance(attr, BenchlingConnection) and (
-            benchling_tenant == attr.tenant_name
-            or benchling_tenant == attr.tenant_alias
-        ):
+        bc = getattr(module, attr_name)
+        if isinstance(bc, BenchlingConnection):
+            if not (
+                benchling_tenant == bc.tenant_name
+                or benchling_tenant == bc.tenant_alias
+            ):
+                raise Exception(
+                    f"tenant name {benchling_tenant} does not match tenant name {bc.tenant_name} or alias {bc.tenant_alias} in liminal/env.py."
+                )
+            if not bc.api_client_id or not bc.api_client_secret:
+                raise Exception(
+                    "api_client_id and api_client_secret must be provided in BenchlingConnection in liminal/env.py. This is necessary for the migration service."
+                )
+            if not bc.internal_api_admin_email or not bc.internal_api_admin_password:
+                raise Exception(
+                    "internal_api_admin_email and internal_api_admin_password must be provided in BenchlingConnection in liminal/env.py. This is necessary for the migration service."
+                )
             try:
                 current_revision_id: str = getattr(
-                    module, attr.current_revision_id_var_name
+                    module, bc.current_revision_id_var_name
                 )
-                return current_revision_id, attr
+                return current_revision_id, bc
             except Exception as e:
                 raise Exception(
-                    f"CURRENT_REVISION_ID variable not found in liminal/env.py. Given variable name: {attr.current_revision_id_var_name}"
+                    f"CURRENT_REVISION_ID variable not found in liminal/env.py. Given variable name: {bc.current_revision_id_var_name}"
                 ) from e
     raise Exception(
-        f"BenchlingConnection with tenant_name {benchling_tenant} not found in liminal/env.py. Please update the env.py file with the correctly defined BenchlingConnection."
+        "BenchlingConnection not found in liminal/env.py. Please update the env.py file with a correctly defined BenchlingConnection."
     )
 
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/orm/column.py

@@ -15,21 +15,21 @@ class Column(SqlColumn):
 
     Parameters
     ----------
-    name : str | None
+    name : str
         The external facing name of the field.
-    type : BenchlingFieldType | None
+    type : BenchlingFieldType
         The type of the field.
-    required : bool | None
+    required : bool
         Whether the field is required.
-    is_multi : bool | None
+    is_multi : bool = False
         Whether the field is a multi-value field.
-    parent_link : bool | None
+    parent_link : bool = False
         Whether the entity link field is a parent of the entity schema.
-    dropdown : str | None
-        The name of the dropdown for the field.
-    entity_link : str | None
+    dropdown : Type[BaseDropdown] | None = None
+        The dropdown for the field.
+    entity_link : str | None = None
         The warehouse name of the entity the field links to.
-    tooltip : str | None
+    tooltip : str | None = None
         The tooltip text for the field.
     """
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/liminal/utils.py

@@ -9,14 +9,14 @@ from liminal.connection.benchling_service import BenchlingService
 
 def pascalize(input_string: str) -> str:
     return "".join(
-        re.sub(r"[\[\]{}()]", "", word).capitalize()
+        re.sub(r"[\[\]{}():]", "", word).capitalize()
         for word in re.split(r"[ /_\-]", input_string)
     )
 
 
 def to_snake_case(input_string: str) -> str:
     return "_".join(
-        re.sub(r"[\[\]{}()]", "", word).lower()
+        re.sub(r"[\[\]{}():]", "", word).lower()
         for word in re.split(r"[ /_\-]", input_string)
     )
 

{liminal_orm-1.0.3.dev1 → liminal_orm-1.0.4}/pyproject.toml

@@ -1,11 +1,17 @@
 [tool.poetry]
 name = "liminal-orm"
-version = "1.0.3.dev1"
+version = "1.0.4"
 description = "An ORM and toolkit that builds on top of Benchling's platform to keep your schemas and downstream code dependencies in sync."
 authors = ["DynoTx Open Source <opensource@dynotx.com>"]
 readme = "README.md"
+homepage = "https://github.com/dynotx/liminal-orm"
+repository = "https://github.com/dynotx/liminal-orm"
+documentation = "https://dynotx.github.io/liminal-orm/"
 packages = [{include = "liminal"}]
 
+[tool.poetry.urls]
+"Bug Tracker" = "https://github.com/dynotx/liminal-orm/issues"
+
 [tool.poetry.dependencies]
 python = ">=3.9,<4"
 benchling-sdk = ">=1.8.0"
@@ -22,7 +28,7 @@ lxml = "^5.3.0"
 [tool.poetry.group.dev.dependencies]
 ipykernel = "^6.29.5"
 mkdocs-material = "^9.5.41"
-mypy = "^1.11.2"
+mypy = "^1.1.1"
 pre-commit = "^4.0.1"
 pytest = "^8.3.3"
 ruff = "^0.6.9"