-
Notifications
You must be signed in to change notification settings - Fork 41
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
docName constraint interacts badly with -latest convention for editors' drafts #439
Comments
@henrik@levkowetz.com changed component from |
@henrik@levkowetz.com commented I wonder if you might profitably use the warning suppression feature for v3 formatters to suppress this? If you add this before , you should not see the warning:
(It uses prefix matching and if that fails then regex matching to check if a given warning should be silenced). |
@henrik@levkowetz.com changed priority from |
@rjsparks@nostrum.com changed status from |
@rjsparks@nostrum.com changed resolution from `` to |
@rjsparks@nostrum.com commented The suggestion Henrik makes looks like the right path for now. Marking this WontFix. |
@julian.reschke@gmx.de commented Seems like the wrong decision to me. |
@julian.reschke@gmx.de commented This is bad.
|
resolution_wontfix
type_defect
| by jyasskin@chromium.orgWhen using https://github.com/martinthomson/i-d-template/, the documentation instructs us to use "the -latest suffix in place of the usual number ('-00', or '-08')." The build system replaces that with the right number in the process of submitting.
However, when I have this build system pass the --v3 parameter to xml2rfc, xml2rfc complains:
Clearly that's the right warning for actually submitting documents, but it would be nice if it didn't appear while developing them, as is the case in xml2rfc v2.
Issue migrated from trac:439 at 2022-02-05 12:50:58 +0000
The text was updated successfully, but these errors were encountered: