You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is the same bug as in #1572. However, I don't understand why the issue is closed.
I understand why the issue occurs, and that it is due to the way keyrefs are currently resolved (using this page):
A temporary list of files that have keyrefs is created, and only these files get key resolution. Since conrefpush occurs after this list is created (but before the key resolution itself), the target files of a conrefpush that don't have key references are not part of this list, thus ignored.
However, the fact that the current design doesn't enable it doesn't mean the bug doesn't exist. A user would expect these keys to be resolved.
If push conref adds content with a keyref into a topic that doesn't already have keyrefs, the topic will not be processed for keyref resolution.
The text was updated successfully, but these errors were encountered: