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
{{ message }}
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
This is a new specification for Clara's Command Holder. Designated as Command Holder Revision 3 slated for 0.5.0 Sparkling Satania.
The Autoreload system
The command holder inspects a command folder's contents and if it sees a file change on the main file or it's dependents, it enforces a hot auto-reload. This should be only logged at the console and silent from the Discord side.
Snapshot system
This is in par with the autoreload system. once the CommandHolder detects there is a file change, it quickly saves the previously-loaded command object and "snpashots" it and stores on a volatile storage. It has two conditions, if the newer command object successfully inits and works without errors, the snapshotted object is discarded however if the newer command object fails to load properly, the Command Holder has to use the "last known good snapshot" of the command object.
The text was updated successfully, but these errors were encountered:
Please be noted we'll handle the snapshots under a different class named Snapshotter. This would be the module that the CommandHolder would dump the previous version of the command object after it has hot reloaded the latest revision. Only allow one copy of the object per command
This is a new specification for Clara's Command Holder. Designated as Command Holder Revision 3 slated for 0.5.0 Sparkling Satania.
The Autoreload system
The command holder inspects a command folder's contents and if it sees a file change on the main file or it's dependents, it enforces a hot auto-reload. This should be only logged at the console and silent from the Discord side.
Snapshot system
This is in par with the autoreload system. once the CommandHolder detects there is a file change, it quickly saves the previously-loaded command object and "snpashots" it and stores on a volatile storage. It has two conditions, if the newer command object successfully inits and works without errors, the snapshotted object is discarded however if the newer command object fails to load properly, the Command Holder has to use the "last known good snapshot" of the command object.
The text was updated successfully, but these errors were encountered: