Brings CreateNewVersionInProject up to parity with SpeckePy #3298
Conversation
This file contains 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
|
Oh! Nice catch @secretlyagoblin 🙌🏼 🙇🏼♂️ We'll get this in ASAP, pending a chat with the team. |
AlanRynne
approved these changes
Apr 22, 2024
BovineOx
approved these changes
Apr 25, 2024
JR-Morgan
approved these changes
Apr 25, 2024
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.
Per the issue logged in the Automate Bug reports in February:
https://speckle.community/t/automate-bug-reports/9136/20
The functionality in this PR wasn't hooked up - you can compare it to the same lines in Specklepy: https://github.com/specklesystems/specklepy/blob/6469b6f757f00bb93041a835c04da71ceff1d3d6/src/speckle_automate/automation_context.py#L162
So the Resulting Models subsection in for automations isn't populating in C#