OverrideAudit 3.0.0
This release is the next major version bump for OverrideAudit, migrating it away from the Python 3.3 plugin in preparation for the next development cycle of Sublime Text, which will bump the Python version to the current release.
❗ As of this version, OverrideAudit requires Sublime Text build 4200 or higher (previously it was 4126); this is the current stable version of Sublime at this point in time. This was done with an eye towards not wanting to keep backward compatability with older Python and the various code changes that need to be present for us to work on that version.
-
Update OverrideAudit to officially use the Python 3.8 plugin host rather than the legacy plugin host. The legacy host is going away and there were some beneficial changes to be made while bringing everything more up to date.
-
Fix some minor edge case bugs that could trigger in obscure cases and cause console errors. Some of these were related to running in the newer 3.8 plugin host, where some call signatures worked a bit differently.
-
Fix an issue with the package hover popup for some reports displaying an incorrect count of overrides. Previously it assumed a minimum of 1 override if any were possible, which is wrong and caused the popup to display incorrect counts. Now it is smart enough to know if there are any at all. The actual count is still obscured in the
Package Report, which is meant to be quick (gathering the override count requires scanning the contents of all packages). -
Update handling of the Python version that displays in the hover popup so that it always displays even if there are no plugins, and make the reported version more correct based on upcoming changes to the Python version used by Sublime. This now more closely follows how Sublime works in this regard, and should be future proof in as much as it gathers the versions of all possible plugin hosts that exist rather than having values be hard coded.
-
If a package declares an invalid Python version, mention in the hover popup that plugins are ignored in that package as a result (Sublime displays a message to this effect in the console when the package loads).
-
Update the metadata that's used to provide information for packages that ship with Sublime directly to include new packages that have been added to the standard Sublime distribution since the metadata was originaly added.
-
Mark the dependencies that display in the package report as "legacy-style" dependencies, since with PC 4+, all most all dependencies are installed as actual libraries outside of the Packages folder. For the time being this functionality is still present, and probably will be for the forseeable future until the package ecosystem solidifies and everyone is using a new Packge Control version.