anyproto / anyproto/anytype-api
Names of links in Markdown body is not always updating by Get Object
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 113
- Forks
- 20
- Avg merge
- 16m
- Merged PRs (30d)
- 1
Description
Have you read a contributing guide?
- I have read CONTRIBUTING.md
- I have searched the existing issues and didn't find any that were similar
- I have considered creating a pull request with fixes instead of a bug report and want to proceed
Current Behavior
Links in markdown body is not updating if I update some anytype-links what are in AnyType object.
Expected Behavior
I always have latest markdown body by "Get object" method in API
Steps To Reproduce
- Create object1 and old_object2
- Create link to old_object2 in body of object1
- Change name of old_object2 ot new_object2
- get object1 by API and check Markdown body, it will be old_object2
additionally: - If you did some changes in object1 markdown body will be updated and old_object2 became new_object2
Environment
OS version: darwin arm64 15.6.0
App version: 0.48.5
Build number: build on 2025-08-14 14:26:54 +0000 UTC at #349da9ee9b99abcc6566b66c746d8d80b74e9870
Library version: v0.42.4
Anything else?
Video:
https://github.com/user-attachments/assets/b150d768-34e8-40da-ad28-5a10eba4de3d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the API's Get object method and reproduce the steps using object1 and a renamed linked object. Check when the Markdown body is generated or refreshed, then verify that fetching object1 after the linked object's name changes returns the new name without requiring an edit to object1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100