Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an option to consider variables already saved in save file #6

Open
steve02081504 opened this issue Jul 16, 2022 · 1 comment

Comments

@steve02081504
Copy link

Considering the archive file in this way can significantly reduce the number of undefined variables read by false positives
At the same time, it might be possible to in turn find variables that are defined in the archive file but not used in the dic file and give a warning(perhaps with a regular expression group for ignore)

@steve02081504
Copy link
Author

In case I'm being too vague and making it difficult to understand, I'll explain in more detail
What I mean is to provide an optional function to consider save file like yaya_variable.cfg, and to consider variables that already exist in this archive file as defined variables, and to consider warning about variables that are in the save file but not used in the dic file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant