Hi @EricM,

Great questions!

Pinning an update pins it to the top of a specific item, not multiple items.

Let’s say you have 3 updates - you can pin one (or more) the top to ensure that the pinned update is listed at the beginning (no matter when it was created).

Regarding the arguments, I understand what you’re saying! That’s currently how the mutation is built, but I’m happy to bring this to the attention of our dev teams.

Let us know if you have any other questions!

Best,

Rachel

Hi @rachelatmonday ,

Thank you for your reply. This is my understanding as well. So can I expect this field to always return one item_id despite it being an array/list in GraphQL terms?

This should have been a simple true/value field unless I’m missing something, e.g: pinned_to_top : true.

That’s currently how the mutation is built, but I’m happy to bring this to the attention of our dev teams.

I would expect the update ID to be sufficient and its corresponding item_id to be automatically resolved logically, but I can work around this.

Also there’s another possible technical issue I noticed. The item_id argument for pin_to_top and unpin_from_top is an Int! type.

Hi @EricM,

The team mentioned that both arguments are required because an update can appear on other items (not only the parent item) if you mention an item in the update. They are looking into the usage of this feature and may make updates accordingly.

I reported the ID vs Int discrepancy to the team yesterday, and they are on it. All changes will be announced in the changelog so make sure to follow along there.

Best,

Rachel

Hi again @EricM,

Docs will be updated soon, but just wanted to let you know that the team addressed both of these issues. They’re in 2024-10.

Try it out and let me know if you have any problems!

Best,

Rachel

Thank you for the update and looking into this. I tested 2024-10, and item_id in both mutations (pin_to_top and unpin_from_top) is of ID type and not required.