Fix: HybridObjects with the same name are not included correctly in C++#1281
Open
NotGeorgeMessier wants to merge 11 commits intomrousavy:mainfrom
Open
Fix: HybridObjects with the same name are not included correctly in C++#1281NotGeorgeMessier wants to merge 11 commits intomrousavy:mainfrom
NotGeorgeMessier wants to merge 11 commits intomrousavy:mainfrom
Conversation
|
Someone is attempting to deploy a commit to the Margelo Team on Vercel. A member of the Team first needs to authorize it. |
added 2 commits
April 3, 2026 04:17
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Another option for issue #1278
It might be not ideal but its working.
Added new hybrid objects and new hybrid views to the external package with the same name to make sure nothing causes conflicts.
Tested on:
iOS | example app | no/static/dynamic frameworks | build + all tests (+ new) + all views (+ new) ✅
Android | example app | build + all tests (+ new) + all views (+ new) ✅
iOS | my side project app | no/static/dynamic frameworks ✅
Backward compatible - yes
Migration for packages needed - yes: update include for Spec in user written cpp, replace create hybrid object and get host component by generated ts functions