@travetto/registry 3.0.2-rc.1 → 3.0.3

package/README.md

@@ -1,6 +1,7 @@
 <!-- This file was generated by @travetto/doc and should not be modified directly -->
-<!-- Please modify https://github.com/travetto/travetto/tree/main/module/registry/DOC.ts and execute "npx trv doc" to rebuild -->
+<!-- Please modify https://github.com/travetto/travetto/tree/main/module/registry/DOC.tsx and execute "npx trv doc" to rebuild -->
 # Registry
+
 ## Patterns and utilities for handling registration of metadata and functionality for run-time use
 
 **Install: @travetto/registry**
@@ -18,14 +19,10 @@ This module is the backbone for all "discovered" and "registered" behaviors with
 Registration, within the framework flows throw two main use cases:
 
 ### Initial Flows
-
 The primary flow occurs on initialization of the application. At that point, the module will:
-
-   
-   1. Initialize [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts) and will automatically register/load all relevant files
+   1. Initialize [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts#L10) and will automatically register/load all relevant files
    1. As files are imported, decorators within the files will record various metadata relevant to the respective registries
-   1. When all files are processed, the [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts) is finished, and it will signal to anything waiting on registered data that its free to use it.
-
+   1. When all files are processed, the [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts#L10) is finished, and it will signal to anything waiting on registered data that its free to use it.
 This flow ensures all files are loaded and processed before application starts. A sample registry could like:
 
 **Code: Sample Registry**
@@ -75,16 +72,16 @@ export class SampleRegistry extends MetadataRegistry<Group, Child> {
 The registry is a [MetadataRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/metadata.ts#L13) that similar to the [Schema](https://github.com/travetto/travetto/tree/main/module/schema#readme "Data type registry for runtime validation, reflection and binding.")'s Schema registry and [Dependency Injection](https://github.com/travetto/travetto/tree/main/module/di#readme "Dependency registration/management and injection support.")'s Dependency registry.
 
 ### Live Flow
-At runtime, the registry is designed to listen for changes and to propagate the changes as necessary. In many cases the same file is handled by multiple registries.
+At runtime, the registry is designed to listen for changes and to propagate the changes as necessary. In many cases the same file is handled by multiple registries. 
 
-As the [DynamicFileLoader](https://github.com/travetto/travetto/tree/main/module/base/src/internal/file-loader.ts) notifies that a file has been changed, the [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts) will pick it up, and process it accordingly.
+As the [DynamicFileLoader](https://github.com/travetto/travetto/tree/main/module/base/src/internal/file-loader.ts#L26) notifies that a file has been changed, the [RootRegistry](https://github.com/travetto/travetto/tree/main/module/registry/src/service/root.ts#L10) will pick it up, and process it accordingly.
 
 ## Supporting Metadata
-
-As mentioned in [Manifest](https://github.com/travetto/travetto/tree/main/module/manifest#readme "Support for project indexing, manifesting, along with file watching")'s readme, the framework produces hashes of methods, classes, and functions, to allow for detecting changes to individual parts of the codebase. During the live flow, various registries will inspect this information to determine if action should be taken.  
+As mentioned in [Manifest](https://github.com/travetto/travetto/tree/main/module/manifest#readme "Support for project indexing, manifesting, along with file watching")'s readme, the framework produces hashes of methods, classes, and functions, to allow for detecting changes to individual parts of the codebase. During the live flow, various registries will inspect this information to determine if action should be taken.
 
 **Code: Sample Class Diffing**
 ```typescript
+
 #handleFileChanges(file: string, classes: Class[] = []): void {
     const next = new Map<string, Class>(classes.map(cls => [cls.Ⲑid, cls] as const));
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@travetto/registry",
-  "version": "3.0.2-rc.1",
+  "version": "3.0.3",
   "description": "Patterns and utilities for handling registration of metadata and functionality for run-time use",
   "keywords": [
     "ast-transformations",
@@ -27,10 +27,10 @@
     "directory": "module/registry"
   },
   "dependencies": {
-    "@travetto/base": "^3.0.2-rc.1"
+    "@travetto/base": "^3.0.3"
   },
   "peerDependencies": {
-    "@travetto/transformer": "^3.0.2-rc.1"
+    "@travetto/transformer": "^3.0.3"
   },
   "peerDependenciesMeta": {
     "@travetto/transformer": {