锚文档不存在？ [英] Anchor documentation does not exist?

问题描述

查看Google云端硬盘文档以获取在开发网站上的评论它提到

anchor;串;文档的一个区域表示为JSON字符串。

然而，定位文档的位置在哪里？请参阅定位文档以获取有关如何定义和解释定位属性的详细信息。 ？

解决方案

请参阅 https://developers.google.com/drive/manage-comments 了解详情。

FWIW，锚点目前有点受限。最大的问题是评论上的锚是不可改变的。如果您最终使用自定义方案，并且可以引用内容中唯一可识别的内容（例如，XML元素ID或其他标记），那么您应该没有任何问题。但是在doc上详细描述的其他一些锚定方案是有问题的。例如，如果文件被修改，在锚点位置之前插入一行，则锚定到文本文件中的行将会中断。直到主播是可变的，最好限制自己的自定义计划和/或未锚定的评论。

while looking over the Google Drive documentation for comments here on the dev site it mentions

anchor; string; A region of the document represented as a JSON string. See anchor documentation for details on how to define and interpret anchor properties.

However, where is the anchor documentation?

解决方案

See https://developers.google.com/drive/manage-comments for details.

FWIW, anchors are a bit limited at the moment. The biggest issue is anchors on comments are immutable. If you end up using a custom scheme and can refer to something uniquely identifiable in your content (e.g. an XML element ID or some other marker) then you shouldn't have any issues. But some of the other anchor schemes detailed on the doc are problematic. For example anchoring to a line in a text file will break if the file is modified an a line is inserted before the anchor location. Until anchors are mutable, best to limit your self to custom schemes and/or unanchored comments.

这篇关于锚文档不存在？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！