You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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
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)
The text was updated successfully, but these errors were encountered: