You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `QueryManager` currently uses `Type.name` to generate query keys.
167
-
In minified builds, class names are reduced to single letters (`a`, `b`, `c`...), causing potential collisions between different queries.
168
-
169
-
Possible solutions:
170
-
- Numeric registry with auto-incrementing ID for each component type
171
-
-`Symbol()` associated with each class
172
-
- Decorator or static method that assigns a unique identifier
173
-
174
-
---
175
-
176
160
### 🟠 Improvements
177
161
178
162
Optimizations and refinements that improve quality and performance.
@@ -193,12 +177,6 @@ Ideas and possible evolutions to evaluate based on needs.
193
177
194
178
> ⚠️ Evaluate carefully: could complicate the API and go against the project's "DX-first" philosophy.
195
179
196
-
-[ ]**Archetypes**
197
-
198
-
Consider an archetype system to group entities with the same component "signature", optimizing queries.
199
-
200
-
> ⚠️ In a JavaScript context, the traditional benefits of archetypes (cache locality, contiguous memory) are not exploitable. The cached View system already present in `QueryManager` covers part of these advantages. Actual utility to be evaluated.
0 commit comments