EnderShadow8
EnderShadow8
@NateTheGreatt > 1. the compiler will obfuscate the real underlying type of `TypedArray` and its own suite of methods such as `set`, `subarray`, etc which `Array` type does not have...
@NateTheGreatt > @EnderShadow8 here is a screenshot of what I meant (with your typings applied): >  > all of these highlighted properties (`flat`, `push`, `pop`, etc) do not exist...
> when my clients connect the first time, a particular entity id associated with a some of the client state is e.g. eid=601, then when that client disconnects/reconnects, next time...
Is there any reason you want the id to be the same across runs? Since you did a reset, there's no previous information to compare against, so ideally you wouldn't...
I think I see what you're trying to do now, it's probably best to see what Nate says about this
Good idea. You could of course implement this yourself, but I think this is a very common use case so I'll add it to the library.
I've thought about this for a bit, and doing a deep equality check against every query created seems a bit excessive for the problem at hand, especially since extra queries...
That shouldn't happen. What version are you using? `defineComponent` creates a component storage under the hood, but if you have your own custom storage then you would `registerComponent` it.
Ah. Better add `.vscode` to `.gitignore`.
Fixed the git history, after I nuked it with rebase. Everything should be ok to merge now