Skip to content

feat(model): grid check with files#136

Merged
mostaphaRoudsari merged 1 commit intopollination:masterfrom
AntonelloDN:master
May 16, 2023
Merged

feat(model): grid check with files#136
mostaphaRoudsari merged 1 commit intopollination:masterfrom
AntonelloDN:master

Conversation

@AntonelloDN
Copy link
Copy Markdown
Contributor

@mostaphaRoudsari mostaphaRoudsari merged commit 62fe930 into pollination:master May 16, 2023
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 0.10.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

chriswmackey added a commit to chriswmackey/handlers-python that referenced this pull request Sep 18, 2023
We used to have the Model handler set up such that, if you just connected up the file path to a HBJSON, the file would just get copied for upload without loading it into Python. [It seems that we changed this a few months ago](pollination@62fe930) but we should revert it since being able to plugin in a file path instead of a Model object and know that extra time wouldn't be spent saving or re-parsing it was really useful.

From my understanding, the re-parsing routine was added a few months ago because of checks that we wanted to run from the Rhino plugin but, for a case like that, the check should be run on the .NET side where we have the Rhino plugin Model object in .NET form instead of writing a large .NET Model object to JSON, loading the model from JSON to Python, running the check in Python, and then writing the Model from Python back to JSON. [It's for cases like this that we have handlers that are written in .NET.](https://github.com/pollination/handlers-csharp)
chriswmackey added a commit that referenced this pull request Sep 18, 2023
We used to have the Model handler set up such that, if you just connected up the file path to a HBJSON, the file would just get copied for upload without loading it into Python. [It seems that we changed this a few months ago](62fe930) but we should revert it since being able to plugin in a file path instead of a Model object and know that extra time wouldn't be spent saving or re-parsing it was really useful.

From my understanding, the re-parsing routine was added a few months ago because of checks that we wanted to run from the Rhino plugin but, for a case like that, the check should be run on the .NET side where we have the Rhino plugin Model object in .NET form instead of writing a large .NET Model object to JSON, loading the model from JSON to Python, running the check in Python, and then writing the Model from Python back to JSON. [It's for cases like this that we have handlers that are written in .NET.](https://github.com/pollination/handlers-csharp)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants