Draft
Conversation
two modes: - graph: display require graph (pass option `--graph` - check: check for unsafe usage of globals, do not pass `--graph` example usage: `lute run .\checks\checkAll.luau` `lute run .\checks\checkAll.luau --graph`
Collaborator
Author
|
with lute we can also implement secret validation; ex if |
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
1 participant
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.
currently implemented with lute is a worker manager contract validator
the checkAll script currently has two modes:
--graph)--graphexample usage:
lute run .\checks\checkAll.luaulute run .\checks\checkAll.luau --graphalso its not a hard requirement that we will use arrowcrab as a graph, or even have a graph in the first place, just thought it would be good to visualize
in the future, we can also implement the package manager idea (#21) with pesde + simple lute scripts that can localize used globals
note! currently this script emits a file with ~639 entries of unsafe global usage in worker manager code, which should also be addressed