-
CREATE TABLE IF NOT EXISTS _new_matchup_stats (
archetype_id INT NOT NULL,
opponent_archetype_id INT NOT NULL,
season_id INT NOT NULL,
wins INT …
-
### Backstory
* https://github.com/rerun-io/rerun/issues/3279
* https://github.com/rerun-io/rerun/issues/3341
What should the following code do:
```rs
log("points", Points3D::new(positions).w…
emilk updated
2 months ago
-
Currently, using `:without(Components.B)` in a query is similar to querying normally, using `world:get(Components.B)` to check if the component is present, and using `continue` to skip the iteration (…
-
CREATE TABLE IF NOT EXISTS _new_season_archetype_playability (
name VARCHAR(190) NOT NULL,
season_id INT NOT NULL,
archetype_id INT NOT NULL,
pl…
-
### Brief Summary
After updating the maven-compiler-plugin from version 3.8.1 to 3.13.0 using JDK17 the compiler shows a warning:
LEVEL: WARNING, MESSAGE: Supported source version 'RELEASE_7' from…
-
Let's start this as a brainstorm for supporting multiple builder archetypes
### Questions
- [ ] Do we _want_ multiple archetypes supported?
- (I'm assuming so, would be nice to split up client test …
-
Courtesy of @chaseadamsio
The idea is that `ARCHETYPE/package.json` has some warts from the `scripts` not really being for the archetype's dev / release workflow but for builder projects. This would…
-
-
@sbailey @abhi0395 can we use this ticket to flesh out what changes we would need to make to Redrock to support archetype-only fitting? In other words, at the moment I believe that archetypes can only…
-
The current layout of component data is very simple, but it leaves a lot to be desired in terms of performance and compactness.
Each level has a component container which is essentially a map from…