Skip to content

Do not create regions that will not be used in the rando - #26

Merged
CodeTriangle merged 1 commit into
crosscode-devfrom
nonexistent-regions
Jul 30, 2026
Merged

Do not create regions that will not be used in the rando#26
CodeTriangle merged 1 commit into
crosscode-devfrom
nonexistent-regions

Conversation

@CodeTriangle

Copy link
Copy Markdown
Owner

this commit does a lot of things:

  • region connections now support metadata
  • region data no longer contains a list of regions
  • regions are created on-demand when investigating region connections in logic
  • Pools.__should_include has been turned into a public member for ease of implementation
  • several conditions that rely on region accessibility now check for the existence of those regions to avoid crashes -- this should be treated as a temporary fix

this commit does a lot of things:
* region connections now support metadata
* region data no longer contains a list of regions
* regions are created on-demand when investigating region connections in logic
* Pools.__should_include has been turned into a public member for ease of implementation
* several conditions that rely on region accessibility now check for the existence of those regions to avoid crashes -- this should be treated as a temporary fix
@CodeTriangle

Copy link
Copy Markdown
OwnerAuthor

@Gudf please confirm this is suitable for your purposes

@Gudf

Gudf commented Jul 29, 2026

Copy link
Copy Markdown

Yup, looks good to me!

@CodeTriangle
CodeTriangle merged commit 09852b2 into crosscode-devJul 30, 2026
6 of 20 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@CodeTriangle@Gudf