cleanup 2

spicywebau · Jun 23, 2021 · 46fb39d · 46fb39d
1 parent 8c21a7b
commit 46fb39d
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 21 deletions.
diff --git a/src/SpicyAfterpay.php b/src/SpicyAfterpay.php
@@ -12,11 +12,7 @@
 
 use Craft;
 use craft\base\Plugin;
-use craft\services\Plugins;
-use craft\events\PluginEvent;
-use craft\web\UrlManager;
 use craft\web\twig\variables\CraftVariable;
-use craft\events\RegisterUrlRulesEvent;
 use craft\commerce\services\Gateways;
 use craft\events\RegisterComponentTypesEvent;
 
@@ -30,15 +26,6 @@
 use yii\base\Event;
 
 /**
- * Craft plugins are very much like little applications in and of themselves. We’ve made
- * it as simple as we can, but the training wheels are off. A little prior knowledge is
- * going to be required to write a plugin.
- *
- * For the purposes of the plugin docs, we’re going to assume that you know PHP and SQL,
- * as well as some semi-advanced concepts like object-oriented programming and PHP namespaces.
- *
- * https://docs.craftcms.com/v3/extend/
- *
  * @author    Spicy Web
  * @package   SpicyAfterpay
  * @since     0.1.0

diff --git a/src/services/SpicyAfterpayService.php b/src/services/SpicyAfterpayService.php
@@ -21,14 +21,6 @@
 use yii\base\InvalidConfigException;
 
 /**
- * SpicyAfterpayService Service
- *
- * All of your plugin’s business logic should go in services, including saving data,
- * retrieving data, etc. They provide APIs that your controllers, template variables,
- * and other plugins can interact with.
- *
- * https://craftcms.com/docs/plugins/services
- *
  * @author    Spicy Web
  * @package   SpicyAfterpay
  * @since     0.1.0