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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,4 @@ When contributing to this repository, please do not feel intimidated! We welcome
15
15
including indent style etc).
16
16
7. Your PR must pass the CI actions before being allowed to be merged. Our PR actions check that the
17
17
build will compile on various platforms before release and makes precompiled versions of the library.
18
-
8. If you are on the discord server for the project and your PR is accepted, let a moderator know and we
19
-
will grant you the 'Contributors' role.
20
-
18
+
8. Automated changes e.g. via grammarly or a static analysis tool will not usually be accepted into the code without proper thought out justification (by a human being, not an AI or an App) as to why the changes are required. Generally a PR should do more than fix a single spelling error for example as this just takes precious time for something which could be resolved a direct commit to the dev branch.
We keep things marked as depreciated until next major API version.
6
+
If discord removes the function, we may remove the method from the library or replace it with a thrown exception depending on the type of function and at our discretion.
7
+
Such functions which are made to throw will then be removed at the next major API version.
* @brief Resolved snowflake ids to users, guild members, roles and channels.
477
+
* @brief Resolved snowflake ids to users, guild members, roles and channels. You can use the `interaction::get_resolved_*` methods to easily get a resolved set
478
478
*/
479
479
structDPP_EXPORT command_resolved {
480
480
/**
@@ -695,7 +695,7 @@ class DPP_EXPORT interaction : public managed, public json_interface<interaction
695
695
user usr; //!< User object for the invoking user
696
696
std::string token; //!< a continuation token for responding to the interaction
* @param callback Function to call when the API call completes.
2660
+
* On success the callback will contain a dpp::onboarding object in confirmation_callback_t::value filled to match the vanity url. On failure, the value is undefined and confirmation_callback_t::is_error() method will return true. You can obtain full error details with confirmation_callback_t::get_error().
* @brief Edit the guild's onboarding configuration
2666
+
*
2667
+
* Requires the `MANAGE_GUILD` and `MANAGE_ROLES` permissions.
2668
+
*
2669
+
* @note Onboarding enforces constraints when enabled. These constraints are that there must be at least 7 Default Channels and at least 5 of them must allow sending messages to the \@everyone role. The `onboarding::mode` field modifies what is considered when enforcing these constraints.
* @note This method supports audit log reasons set by the cluster::set_audit_reason() method.
2673
+
* @param o The onboarding object
2674
+
* @param callback Function to call when the API call completes.
2675
+
* On success the callback will contain a dpp::onboarding object in confirmation_callback_t::value filled to match the vanity url. On failure, the value is undefined and confirmation_callback_t::is_error() method will return true. You can obtain full error details with confirmation_callback_t::get_error().
2676
+
*/
2677
+
voidguild_edit_onboarding(conststructonboarding& o, command_completion_event_t callback = utility::log_error());
2678
+
2679
+
/**
2680
+
* @brief Get the guild's welcome screen
2681
+
*
2682
+
* If the welcome screen is not enabled, the `MANAGE_GUILD` permission is required.
* @param guild_id The guild ID to get the welcome screen from
2686
+
* @param callback Function to call when the API call completes.
2687
+
* On success the callback will contain a dpp::welcome_screen object in confirmation_callback_t::value filled to match the vanity url. On failure, the value is undefined and confirmation_callback_t::is_error() method will return true. You can obtain full error details with confirmation_callback_t::get_error().
* @param guild_id The guild ID to edit the welcome screen for
2698
+
* @param welcome_screen The welcome screen
2699
+
* @param enabled Whether the welcome screen should be enabled or disabled
2700
+
* @param callback Function to call when the API call completes.
2701
+
* On success the callback will contain a dpp::welcome_screen object in confirmation_callback_t::value filled to match the vanity url. On failure, the value is undefined and confirmation_callback_t::is_error() method will return true. You can obtain full error details with confirmation_callback_t::get_error().
0 commit comments