BUGFIX: Add baseBuilder property in MiniAppManifest type and let it include in withValidManifest
#2549
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.
What changed? Why?

Resolved #2512
On the miniapp registration page on base.dev, you’re required to add
baseBuilders.ownerAddresstomanifest.json, but it’s being omitted bywithValidManifest().Added
baseBuilderfield support toMiniAppManifest.BaseBuilderFieldstype withownerAddressas a required fieldbaseBuildervalidation inwithValidManifestfunctionbaseBuilderin manifest whenownerAddressis presentNotes to reviewers
Follows the same validation pattern as
accountAssociation. WhenbaseBuilderis provided butownerAddressis empty/undefined, it logs a warning and omits from the manifest.How has it been tested?
Added unit tests for
baseBuilderhandling:ownerAddressis undefined/empty stringbaseBuilderis not providedownerAddressis presentaccountAssociationandbaseBuildercan coexist