Objects to use id's instead of key value in search

[PixelFromTheMixery]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing requests and didn't find any that were similar
• I have considered creating a pull request instead and want to proceed

Clear and concise description of the problem

During my setup of my first space, I deleted the original Task and Project Objects to make my own. While this has been fine within the AnyType UI, this has made it undetectable by type in the api space (eg. {"types":["task"]}) and returns zero results. This has been confirmed when trying the same query on a new 'test' space where I haven't performed the same action yet and this DID return results.
I suspect it's looking for an old reference, and finding none nothing fits the filter.

Suggested solution

Supply a type/object id or a type name in the search types payload.
(eg. {"types":["fdwufcwl2.da"]})

Alternative

No response

Additional context

https://github.com/anyproto/.github/blob/main/docs/issues?q=label%3Aenhancement does not lead to anything on the contribution guide

[jmetrikat]

hi @PixelFromTheMixery, could you check the keys for your custom-created types? the endpoint to list types will provide that information.

i believe your filtering issue can be easily resolved by updating the keys of your types to match the keys you want to use for filtering in search. at the moment, they might not be 'task' and 'project', but you can simply rename them.

you can prevent this by explicitly setting the type key when creating types; otherwise, the key is auto-generated from the name in snake_case. always specify the key if you want predictable type filtering behavior :)

filtering by id is also possible (though undocumented), but using keys is the preferred approach.

[PixelFromTheMixery]

Hi @jmetrikat!
I already did so in my troubleshooting, that's what fave me the impression I should flag this issue with you. Here are the snippets of the discovery.
Here is the type with an example task

Here is the type in the endpoints you described:

{
      "object": "type",
      "id": "bafyreibndjvzmbgsscwgj7wg6t5qxuzqriwijmgtjd2thb4qwlmzvwotde",
      "key": "task",
      "name": "Task",
      "plural_name": "Tasks",
      "icon": {
        "format": "icon",
        "name": "checkbox",
        "color": "purple"
      },
      "archived": false,
      "layout": "basic",
      "properties": [

Here is the search call (bearing in mind that another type, like "collections", does work):

logger.info("Test endpoint called")
    url = "http://localhost:31009/v1/spaces/"
    url += "<space id>/"
    url += "search"
    payload = {"types": ["task"]}
    return make_call("post", url, "getting automation list objects", payload)

Here is the result:

{
  "data": [],
  "pagination": {
    "total": 0,
    "offset": 0,
    "limit": 100,
    "has_more": false
  }
}

Thanks for the thorough message and letting me know that searching by id is possible. edit: I have tried it and it has worked

[jmetrikat]

@PixelFromTheMixery thanks for checking! just to confirm, could you share your anytype version?

i believe i found the issue; it's on our side regarding the mapping of type keys to the search filters. you've deleted the pre-installed type with the key task and created a custom one with the same key. we still resolve deleted types to display correctly for object instances, and that causes a conflict during lookup.. 🫠

as a temporary solution, you can rename the key of your type eg to my_task and key filtering should work fine, until the fix rolls out. i'll think about how to properly solve it. keys should be always unique.

very good catch, thanks for bringing it up!

[PixelFromTheMixery]

Just to confirm!

I did suspect that it was because I deleted the original before I knew I could edit it! Lesson learned for everyone. I would migrate to a new space, but the import data irks me 😅 and I have multiple workarounds now.
Thanks for being a joy to interact with. 😊

[jmetrikat]

thank you :) i'll let you know once it's fixed!