Skip to content

Conversation

@darrelmiller
Copy link
Member

Attempt to fix #415
This is only partial fix. It does ensure that the object model is valid however, due to the way references are resolved we lose the fact that in the original document the reference was to AllPets as it gets collapsed down to Pets. More investigation is required.

@darrelmiller darrelmiller added this to the 1.1.5 milestone Sep 15, 2019
@darrelmiller darrelmiller removed this from the 1.1.5 milestone Dec 7, 2019
@darrelmiller darrelmiller changed the base branch from master to vnext January 4, 2020 21:32
@darrelmiller
Copy link
Member Author

This partial fix should be merged because it is better than not having it there. I still don't know how we can make these references to references actually roundtrip.

@darrelmiller darrelmiller added this to the 1.2.0 milestone Jan 4, 2020
@darrelmiller darrelmiller merged commit 409e039 into vnext Jan 4, 2020
@darrelmiller darrelmiller deleted the dm/componentreference branch January 4, 2020 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Schema reference not parsed as expected, results in circular reference

2 participants