Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyref not processed for pushed conrefs #1607

Closed
jelovirt opened this issue Dec 3, 2013 · 1 comment
Closed

Keyref not processed for pushed conrefs #1607

jelovirt opened this issue Dec 3, 2013 · 1 comment
Assignees
Labels
bug preprocess priority/medium Medium (or unknown) priority issue
Milestone

Comments

@jelovirt
Copy link
Member

jelovirt commented Dec 3, 2013

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.

@ColinMaudry
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug preprocess priority/medium Medium (or unknown) priority issue
Projects
None yet
Development

No branches or pull requests

2 participants