Skip to content

Fix contradiction in markup resolution #1084

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

catamorphism
Copy link
Collaborator

Previously, this stated that markup resolution MUST always succeed. However, resolution of u: options can fail, so that wasn't true.

Previously, this stated that markup resolution MUST always succeed.
However, resolution of `u:` options can fail, so that wasn't true.
@catamorphism catamorphism requested review from aphillips and eemeli June 28, 2025 00:38
@catamorphism
Copy link
Collaborator Author

Copy link
Collaborator

@eemeli eemeli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While the resolution of individual options can fail, this still holds:

The result of _option resolution_ MUST be a (possibly empty) mapping
of string identifiers to values;
that is, errors MAY be emitted, but such errors MUST NOT be fatal.

In other words, overall resolution of markup will always succeed.

If there is some language in u: options or elsewhere that implies something different, that needs to be fixed rather than changing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants