feat(server): Add metadata to registry nodes in entrypoint implementa… #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…into feature/generic-metadata
Fixes go-orb/go-orb#21 # Conflicts: # client/tests/tests.go
Update test cases to validate the new WithRegistryMetadata functionality replacing previous WithMetadata implementation. This ensures proper testing of the metadata-based server selection feature.
…into feature/generic-metadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add metadata to registry nodes in entrypoint implementations
This PR ensures all entrypoint implementations properly pass their metadata to registry nodes during registration. It completes the metadata functionality requested in go-orb/go-orb#21 by connecting entrypoint configuration with client-side filtering.