Fix serialization of cpp_info when it uses the type field#19604
Merged
franramirez688 merged 3 commits intoconan-io:develop2from Feb 12, 2026
Merged
Fix serialization of cpp_info when it uses the type field#19604franramirez688 merged 3 commits intoconan-io:develop2from
franramirez688 merged 3 commits intoconan-io:develop2from
Conversation
AbrilRBS
commented
Feb 11, 2026
memsharded
approved these changes
Feb 11, 2026
memsharded
approved these changes
Feb 12, 2026
franramirez688
approved these changes
Feb 12, 2026
bentonj-omnissa
pushed a commit
to omnissa-oss-forks/conan
that referenced
this pull request
Feb 12, 2026
…9604) * Fix serialization of cpp_info when it uses the type field * Ue available setter if possible * Fix none Type
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
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.
Changelog: Bugfix: Fix serialization of cpp_info when it uses the type field
Docs: Omit
Closes #19603, but the deserialization approach could probably be a bit better