Renames DoNotDiscover to SkipDiscovery

Author: erikaraujo

src/Web/Blog/articles/2024-10-02-alpha-2.md

@@ -107,7 +107,7 @@ Finally, we made a lot of bugfixes and performance improvements to [discovery](/
 
 ```php
 
-#[DoNotDiscover(except: [MigrationDiscovery::class])]
+#[SkipDiscovery(except: [MigrationDiscovery::class])]
 final class HiddenMigration implements Migration
 {
     /* … */

src/Web/Blog/articles/2024-10-31-alpha-3.md

@@ -153,7 +153,7 @@ public function __invoke(): void
 use Tempest\Generation\ClassManipulator;
 
 new ClassManipulator(PackageMigration::class)
-    ->removeClassAttribute(DoNotDiscover::class)
+    ->removeClassAttribute(SkipDiscovery::class)
     ->setNamespace('App\\Migrations')
     ->print();
 ```

src/Web/Documentation/content/main/1-essentials/02-controllers.md

@@ -287,10 +287,10 @@ use Tempest\Router\HttpMiddleware;
 use Tempest\Router\HttpMiddlewareCallable;
 use Tempest\Router\Request;
 use Tempest\Router\Response;
-use Tempest\Discovery\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 use Tempest\Core\Priority;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 #[Priority(Priority::LOW)]
 final readonly class ValidateWebhook implements HttpMiddleware
 {
@@ -322,12 +322,12 @@ Note that priority is defined using an integer. You can however use one of the b
 
 ### Middleware discovery
 
-Global middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[DoNotDiscover]` attribute:
+Global middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[SkipDiscovery]` attribute:
 
 ```php
-use Tempest\Discovery\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 final readonly class ValidateWebhook implements HttpMiddleware
 { /* … */ }
 ```

src/Web/Documentation/content/main/2-tempest-in-depth/03-events.md

@@ -149,12 +149,12 @@ Note that priority is defined using an integer. You can however use one of the b
 
 ### Middleware discovery
 
-Global event bus middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[DoNotDiscover]` attribute:
+Global event bus middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[SkipDiscovery]` attribute:
 
 ```php
-use Tempest\Discovery\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 final readonly class EventLoggerMiddleware implements EventBusMiddleware
 { /* … */ }
 ```

src/Web/Documentation/content/main/2-tempest-in-depth/08-commands.md

@@ -158,12 +158,12 @@ Note that priority is defined using an integer. You can however use one of the b
 
 ### Middleware discovery
 
-Global command bus middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[DoNotDiscover]` attribute:
+Global command bus middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[SkipDiscovery]` attribute:
 
 ```php
-use Tempest\Discovery\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 final readonly class MyCommandBusMiddleware implements CommandBusMiddleware
 { /* … */ }
 ```

src/Web/Documentation/content/main/3-console/06-middleware.md

@@ -73,12 +73,12 @@ Note that priority is defined using an integer. You can however use one of the b
 
 ### Middleware discovery
 
-Global console middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[DoNotDiscover]` attribute:
+Global console middleware classes are discovered and sorted based on their priority. You can make a middleware class non-global by adding the `#[SkipDiscovery]` attribute:
 
 ```php
-use Tempest\Discovery\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 final readonly class HelloWorldMiddleware implements ConsoleMiddleware
 { /* … */ }
 ```

src/Web/Documentation/content/main/4-internals/05-package-development.md

@@ -4,14 +4,14 @@ title: Package development
 
 Tempest comes with a handful of tools to help third-party package developers.
 
-## DoNotDiscover
+## SkipDiscovery
 
-Tempest has an attribute called `#[DoNotDiscover]`, which you can add on classes. Any class within your package that has this attribute won't be discovered by Tempest. You can still use that class internally, or allow you package to publish it (see [installers](#installers)).
+Tempest has an attribute called `#[SkipDiscovery]`, which you can add on classes. Any class within your package that has this attribute won't be discovered by Tempest. You can still use that class internally, or allow you package to publish it (see [installers](#installers)).
 
 ```php
-use Tempest\Core\DoNotDiscover;
+use Tempest\Discovery\SkipDiscovery;
 
-#[DoNotDiscover]
+#[SkipDiscovery]
 final readonly class UserMigration implements Migration
 {
     // …
@@ -23,9 +23,9 @@ final readonly class UserMigration implements Migration
 Packages can have one or more installers, which can be used to set up your package within a project. For example: a package can optionally publish migration files that will only be discovered when they are published. Take, for example, a look at the `AuthInstaller`, which will install the `User` model, as well as other related models and their migrations:
 
 ```php
-use Tempest\Core\DoNotDiscover;
 use Tempest\Core\Installer;
 use Tempest\Core\PublishesFiles;
+use Tempest\Discovery\SkipDiscovery;
 use Tempest\Generation\ClassManipulator;
 use function Tempest\src_namespace;
 use function Tempest\src_path;
@@ -83,7 +83,7 @@ Running the installer looks like this:
 <success>Done</success>
 ```
 
-Note that you can use `src_path()` to generate paths to the project's source folder. This folder be either `src/` or `app/`, depending on the project's preferences. If you're using the `PublishesFiles` trait, then Tempest will also automatically adjust class namespaces and remove `#[DoNotDiscover]` attributes when publishing files.
+Note that you can use `src_path()` to generate paths to the project's source folder. This folder be either `src/` or `app/`, depending on the project's preferences. If you're using the `PublishesFiles` trait, then Tempest will also automatically adjust class namespaces and remove `#[SkipDiscovery]` attributes when publishing files.
 
 On top of that, you can pass a callback to the `publish()` method, which gives you even more control over the published files: