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
One issue i've noticed with the updateToOne, updateToMany /utils methods is that if your relationships are created but the indexing fails for some reason during the modelling, it will never again try to update the componentsearch catalog and so you wont see the relation in the gui subcomponent.
Im assuming this is because changed_ids will be an empty set so the indexing will get skipped.
Im also assuming that this method does work when there are changes since I know its being used in the Netapp commercial zenpack and it looks to me like i can see all the to/many to/one rels there.
for now im assuming there is a bug somewhere in my modeller preventing the indexing but not the relations. or ive hacked up my dev environment indexing somehow.
but I do think that there should be a check somewhere to see if the relations match the componentsearch catalog so that you can survive a temporary indexing issue (ie zencatalogserver crash/reastart in enterprise, etc)
The text was updated successfully, but these errors were encountered:
My original issue was lack of a custom path reporter which once i set up looked like it fixed things. Even though it looks like i could get the component search indexing to work with an index object in a funky way..now the modelling works every time calling update to one update to many.
One utility that would be nice is a decorator for conv to units with some formatting options for commas in numbers. Also maybe some decorator for f and celcius formatting.
Longer term would be nice to have some guidance on where we should do formattiing. Ie as a method in the object or in the api layer or in js renderers..
Doug, Thanks for the feedback re the decorators. We are trying to figure out where to take zenpack generator next. We are looking to take what we have learned with this first implementation to see if we can iterate it to make future zenpacks easier to iterate on.
I wont close this ticket yet as I want to think about the indexing issue a bit more.
One issue i've noticed with the updateToOne, updateToMany /utils methods is that if your relationships are created but the indexing fails for some reason during the modelling, it will never again try to update the componentsearch catalog and so you wont see the relation in the gui subcomponent.
Im assuming this is because changed_ids will be an empty set so the indexing will get skipped.
Im also assuming that this method does work when there are changes since I know its being used in the Netapp commercial zenpack and it looks to me like i can see all the to/many to/one rels there.
for now im assuming there is a bug somewhere in my modeller preventing the indexing but not the relations. or ive hacked up my dev environment indexing somehow.
but I do think that there should be a check somewhere to see if the relations match the componentsearch catalog so that you can survive a temporary indexing issue (ie zencatalogserver crash/reastart in enterprise, etc)
The text was updated successfully, but these errors were encountered: