Repository navigation
Conversation
- 'get_tasks' and 'get_folders' prepare fields also when default fields are used, so 'ownAttrib' is queried. - 'get_tasks_by_folder_paths' passes 'own_attributes' to 'get_tasks'. - Attribute values are queried for folders and tasks when own attributes are requested, otherwise 'ownAttrib' stayed a list of names. - 'get_project' and 'get_projects' query attributes when own attributes are requested, so the REST projects list is not used. - 'fill_own_attribs' handles empty 'attrib'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
You're passing |
God damn it, skill issue. Stupid IDE. Srry. |
That's been there since beginning, not a new thing. The idea is that you'll get exactly what The reality is that you do care about own attrib when you are handling hierarchy, and in that case it is better to have already in place dictionary with "real entity values" instead of dictionary and list of strings you have to combine to get it. |

Changelog Description
Entities queried with
own_attributes=Truealways containownAttribas a dictionary with attribute values.Additional info
ownAttribwas missing, or was a list of attribute names instead of a dictionary, in these cases:own_attributes=Trueget_tasks(project_name)(default fields)get_tasks_by_folder_paths(...)get_tasks_by_folder_paths(..., fields=...)get_folders(project_name, fields={"id"})get_projects(fields={"name"})Causes:
get_taskscalled_prepare_fieldswithown_attributesonly whenfieldswere passed.get_tasks_by_folder_pathsdid not passown_attributestoget_tasks.ownAttribwas queried without attribute values, so it could not be converted.fill_own_attribsskipped entities with emptyattrib.Testing notes:
own_attributes=True.ownAttribis a dictionary with all attribute names, withNonefor values that are not set on the entity.own_attributesdon't returnownAttrib, as before.