You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the previous version of the speckle server, the commits page provided a view of the commit including, crucially, the commit id. Information about that can be seen on this documentation page: https://speckle.guide/user/web.html
In this image from that page, the "id" at the top refers to the id of the commit (now I believe this is called the version id). In the new version of the Speckle Server frontend, there is no equivalent view of the old "Expand Data View" of the commit object. (note: please let me know if it is available and is something that I've missed).
When using specklepy, it's necessary to know the "commit id" to get the latest model. Our team had developed a workflow where we grabbed the latest commit ID from the expanded data view of the commit object when getting a project from our server instance. It would be nice to be able to access the version id in a way similar to how we used to access the commit id when we developed that workflow.
Describe the solution you'd like
It would be nice would be to add a command to "copy the latest version ID" to the actions on the model card on the project models page.
On the Models page for the Project, each Model (fka branch) has a drop down with options to copy the model id and the link. Since this model (branch) currently has its HEAD at the latest commit/version, it would make sense in my mind to provide a way for the user to copy the commit id at HEAD.
If it would be easier to make the version id copy accessible on the ViewerResourcesViewerCard that might work. That's the view showing the graphical list of versions for a model
The latest version id is used in the calculation of the props for each ViewerResourcesViewerCard. If it's accessible there I would assume it should be accessible elsewhere, hence my suggestion of adding it to the Model card dropdown..
I found out that the version id is used here because the latest version id is actually embedded in the url of the preview image.
The other alternative I've considered is a purely programmatic one in python. However it's possible others may find utility from having the latest version ID easily accessible in the speckle server frontend, so I wanted to propose it.
Additional context
I have experience working with Vue so I'd be willing to give this solution a shot if that would help.
Thanks for your work on this project.
Related issues or community discussions
I searched issues and community discussions but I couldn't find another reference to this.
The text was updated successfully, but these errors were encountered:
On top of what Dim says, the latest version ID is also accessible from the versions page so I'm hesitant to add it to the model card (the versions page is not easy to find though but that's a separate issue).
@benjaminvo In summary, as I understand it, each version of a model has both a Version Id and an object id/commit hash. An example of a Version ID for a model version is 5e9cb42780. An example of an object ID for the same model version is df837b380aefb4ff127b2e6c561943be. The former is accessible on the Version view and the latter is what specklepy needs. I'm trying to get the terminology about this correct but I apologize if I mispeak at all here.
There's a solution in specklepy to grab the latest commit as in the following pseudocode:
Between the raw data model view and the specklepy solution to get the latest commit hash, I can access that object id again.
I wouldn't say no to having easy access to the object id alongside the version id in the version view, but it's now that the Raw Model Data view is back it's possible for me to get it from inside the web app again. I'll close this issue. Thanks for your help.
Prerequisites
What package are you referring to?
frontend-2 only
Is your feature request related to a problem? Please describe.
In the previous version of the speckle server, the commits page provided a view of the commit including, crucially, the commit id. Information about that can be seen on this documentation page: https://speckle.guide/user/web.html
In this image from that page, the "id" at the top refers to the id of the commit (now I believe this is called the version id). In the new version of the Speckle Server frontend, there is no equivalent view of the old "Expand Data View" of the commit object. (note: please let me know if it is available and is something that I've missed).
When using
specklepy
, it's necessary to know the "commit id" to get the latest model. Our team had developed a workflow where we grabbed the latest commit ID from the expanded data view of the commit object when getting a project from our server instance. It would be nice to be able to access the version id in a way similar to how we used to access the commit id when we developed that workflow.Describe the solution you'd like
It would be nice would be to add a command to "copy the latest version ID" to the actions on the model card on the project models page.
On the Models page for the Project, each Model (fka branch) has a drop down with options to copy the model id and the link. Since this model (branch) currently has its HEAD at the latest commit/version, it would make sense in my mind to provide a way for the user to copy the commit id at HEAD.
speckle-server/packages/frontend-2/components/project/page/models/Actions.vue
Line 109 in 2ba6b24
Describe alternatives you've considered
If it would be easier to make the version id copy accessible on the
ViewerResourcesViewerCard
that might work. That's the view showing the graphical list of versions for a modelThe latest version id is used in the calculation of the props for each
ViewerResourcesViewerCard
. If it's accessible there I would assume it should be accessible elsewhere, hence my suggestion of adding it to the Model card dropdown..speckle-server/packages/frontend-2/components/viewer/resources/ModelCard.vue
Line 86 in 2ba6b24
I found out that the version id is used here because the latest version id is actually embedded in the url of the preview image.
The other alternative I've considered is a purely programmatic one in python. However it's possible others may find utility from having the latest version ID easily accessible in the speckle server frontend, so I wanted to propose it.
Additional context
I have experience working with Vue so I'd be willing to give this solution a shot if that would help.
Thanks for your work on this project.
Related issues or community discussions
I searched issues and community discussions but I couldn't find another reference to this.
The text was updated successfully, but these errors were encountered: