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
{{ message }}
This repository was archived by the owner on Jul 25, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 25, 2024. It is now read-only.
does it make sense to remove uuid on object fetch? #106
I find that I am constantly unpacking collections of objects by using the .values() argument. This is because the requests come back with a uuid for the object. I'm thinking maybe that is not all that useful after a few months now. What do you think? I know adding values() is not a huge deal, but since we always use it that way, perhaps we should remove it at the source?
Just a few examples.
environments = list(project.environments(slug__in=",".join(environment_slugs), ordering="slug").values())
suites = list(project.suites(slug__in=",".join(suite_slugs), ordering="slug").values())
for t in list(build.tests(environment=e.id,suite=s.id).values()):
I do remember that in very early prototypes of squad client, we experimented with returning a list of objects but then we found it would be slightly challenging to retrieve a single object without iterating/slicing the list in case the client was used in shell and then we decided to make it a dict. @chaws probably remembers this case.
I find that I am constantly unpacking collections of objects by using the
.values()argument. This is because the requests come back with auuidfor the object. I'm thinking maybe that is not all that useful after a few months now. What do you think? I know addingvalues()is not a huge deal, but since we always use it that way, perhaps we should remove it at the source?Just a few examples.