ephaptic 0.2.0__tar.gz → 0.2.1__tar.gz

{ephaptic-0.2.0 → ephaptic-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ephaptic
-Version: 0.2.0
+Version: 0.2.1
 Summary: The Python client/server package for ephaptic.
 Author-email: uukelele <robustrobot11@gmail.com>
 License: MIT License
@@ -132,6 +132,9 @@ async def add(num1: int, num2: int) -> int:
     return num1 + num2
 ```
 
+> [!TIP]
+> If you're experiencing circular imports, feel free to instead import and use the `expose` function from the library instead of the instance. Please note that if you do this, you must define all exposed functions *before* creating the ephaptic instance - this is mainly for people importing RPC functions from another file. The same thing can be done with the global `identity_loader` decorator.
+
 Yep, it's really that simple.
 
 But what if your code throws an error? No sweat, it just throws up on the frontend, with the error name.

{ephaptic-0.2.0 → ephaptic-0.2.1}/README.md

@@ -90,6 +90,9 @@ async def add(num1: int, num2: int) -> int:
     return num1 + num2
 ```
 
+> [!TIP]
+> If you're experiencing circular imports, feel free to instead import and use the `expose` function from the library instead of the instance. Please note that if you do this, you must define all exposed functions *before* creating the ephaptic instance - this is mainly for people importing RPC functions from another file. The same thing can be done with the global `identity_loader` decorator.
+
 Yep, it's really that simple.
 
 But what if your code throws an error? No sweat, it just throws up on the frontend, with the error name.

{ephaptic-0.2.0 → ephaptic-0.2.1}/ephaptic/__init__.py

@@ -1,6 +1,8 @@
 from .ephaptic import (
     Ephaptic,
-    active_user
+    active_user,
+    expose,
+    identity_loader,
 )
 
 from .client import (

{ephaptic-0.2.0 → ephaptic-0.2.1}/ephaptic/ephaptic.py

@@ -67,6 +67,9 @@ class ConnectionManager:
 
 manager = ConnectionManager()
 
+_EXPOSED_FUNCTIONS = {}
+_IDENTITY_LOADER: Optional[Callable] = None
+
 class EphapticTarget:
     def __init__(self, user_ids: list[str]):
         self.user_ids = user_ids
@@ -76,6 +79,14 @@ class EphapticTarget:
             await manager.broadcast(self.user_ids, name, list(args), dict(kwargs))
         return emitter
     
+def expose(func: Callable):
+    _EXPOSED_FUNCTIONS[func.__name__] = func
+    return func
+    
+def identity_loader(func: Callable):
+    _IDENTITY_LOADER = func
+    return func
+
 class Ephaptic:
     _exposed_functions: Dict[str, Callable] = {}
     _identity_loader: Optional[Callable] = None
@@ -111,6 +122,9 @@ class Ephaptic:
             case _:
                 raise TypeError(f"Unsupported app type: {module}")
             
+        cls._exposed_functions = _EXPOSED_FUNCTIONS.copy()
+        cls._identity_loader = _IDENTITY_LOADER
+
         return instance
 
             

{ephaptic-0.2.0 → ephaptic-0.2.1}/ephaptic.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ephaptic
-Version: 0.2.0
+Version: 0.2.1
 Summary: The Python client/server package for ephaptic.
 Author-email: uukelele <robustrobot11@gmail.com>
 License: MIT License
@@ -132,6 +132,9 @@ async def add(num1: int, num2: int) -> int:
     return num1 + num2
 ```
 
+> [!TIP]
+> If you're experiencing circular imports, feel free to instead import and use the `expose` function from the library instead of the instance. Please note that if you do this, you must define all exposed functions *before* creating the ephaptic instance - this is mainly for people importing RPC functions from another file. The same thing can be done with the global `identity_loader` decorator.
+
 Yep, it's really that simple.
 
 But what if your code throws an error? No sweat, it just throws up on the frontend, with the error name.

{ephaptic-0.2.0 → ephaptic-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ephaptic"
-version = "0.2.0"
+version = "0.2.1"
 authors = [
     { name="uukelele", email="robustrobot11@gmail.com" },
 ]