This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
Implicit controller registration selection #4126
Open
+45
−9
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.
Allows configuration for the features which are used when implicitly registering API controllers. This is necessary when registering a new feature on the full node that includes a controller, but not wanting to include it in the full node web API (for example, wanting to provide a seperate API). Also useful for nodes where you want to provide selective access to the API.
Usage
This doesn't effect explicitly registered controllers.