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

查看:30
本文介绍了锚文件不存在?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

查看 Google Drive 文档以获取评论时在开发网站上 它提到了

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

锚;细绳;表示为 JSON 字符串的文档区域.有关如何定义和解释锚属性的详细信息,请参阅锚文档.

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.

但是,锚文档在哪里?

推荐答案

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

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

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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆