Closed
Conversation
Owner
|
I've created 1.19.2-feat-where branch and merged this into it for now, I want to put some more thought into it before going live with this I also created a discussion #158 to hold relevant syntax proposals |
Cyanox62
added a commit
to Cyanox62/SuperFactoryManager
that referenced
this pull request
Jan 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds WHERE statements onto labelAccess. Allows for filtering of a specific block to pull/push resources based on the contents of that block.
There's a slight quirk of how resources are collected, if the resource tracker doesn't contain the type(s) used in the WHERE statement, those resources will always be 0. This can be mitigated by simply having
0 <resource type>::as part of the resource movement.Could probably use some more debug messages.