| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Makes the creation of the expected diff clearer since the variable has
a name compared to accessing some index of a list.
|
| |
|
|
|
| |
Redundant since test_diff_for_new_updated_and_deleted_roles tests all 3
types together.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Role was being accessed like a class when it is actually a dict.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The whole sync is aborted when an error is caught for simplicity's sake.
The sync message is edited to display the error and the traceback is
logged. To distinguish an error from an abort/timeout, the latter now
uses a warning emoji while the former uses the red cross.
|
| | |
|
| |
|
|
|
|
| |
One is responsible for sending the confirmation prompt while the other
waits for the reaction. The split allows for the confirmation prompt
to be edited with the results of automatic syncs too.
|
| |
|
|
| |
This makes it clearer to users where the notification came from.
|
| | |
|
| |
|
|
|
|
|
| |
* Ignore bot reactions
* Check for core dev role if sync is automatic
* Require author as an argument to _confirm() so it can be compared
against the reaction author
|
| | |
|
| | |
|
| |
|
|
| |
* Mention possibility of timing out as a reason for aborting a sync
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
It doesn't play along well with NamedTuple due to metaclass conflicts.
The workaround involved created a NamedTuple-only base class, which
does work but at the cost of confusing some static type checkers.
Since Diff is now an internal data structure, it no longer really needs
to have precise type annotations. Therefore, a normal namedtuple is
adequate.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The interface was becoming cumbersome to work with so it was all moved
to a single location. Now just calling Syncer.sync() will take care of
everything.
* Remove Optional type annotation from Diff attributes
* _confirm() can edit the original message and use it as the prompt
* Calculate the total diff and compare it against the max before
sending a confirmation prompt
* Remove abort message from sync(); _confirm() will handle that
|
| |
|
|
|
|
|
|
|
|
|
| |
The confirmation prompt will be sent to the dev-core channel or the
specified context. Confirmation is done via reactions and waits 5
minutes before timing out.
* Add name property to Syncers
* Make _get_diff private; only sync() needs to be called now
* Change spelling of synchronize to synchronise
* Update docstrings
|
| |
|
|
|
|
|
|
|
| |
Replaces the functions with a class for each syncer. The classes
inherit from a Syncer base class. A NamedTuple was also created to
replace the tuple of the object differences that was previously being
returned.
* Use namedtuple._asdict to simplify converting namedtuples to JSON
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Use ID from constants directly instead of SYNC_SERVER_ID
* Use f-strings instead of %s for logging
* Fit into margin of 100
* Invert condition to reduce nesting
* Use Any instead of incorrect function annotation for JSON values
|
| |
|
|
| |
Reduces code redundancy.
|
| |
|
|
| |
This seems to have been the intent of the original implementation.
|
| | |
|
| |
|
|
| |
It has a much better guarantee that the cache will be available.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This coroutine waits until the configured guild is available and
ensures the cache is present.
The on_ready event is inadequate because it only waits 2 seconds for a
GUILD_CREATE gateway event before giving up and thus not populating the
cache for unavailable guilds.
|
| |\
| |
| | |
Fix pagniation module for "last page" reaction
|
| |/
|
|
| |
Fixes #746.
|
| |\
| |
| | |
Separate message/embed deletion and reaction deletion emojis
|
| | |
| |
| |
| |
| | |
It could be confused with the delete reaction. Clearing reactions
manually is rarely a useful feature anyway.
|