Re: [Rfc-markdown] kramdown-rfc-extract-sourcecode: Provide better names to the extracted files

[Kesara Rathnayake <[e-mail]>]

> But, as mentioned in the PR, it means there will be a flag day (probably in 1.6.44):

May be time to bump up to 1.7.0 with the breaking changes?
  --Kesara

On Tue, 26 Sept 2023 at 04:12, Carsten Bormann <[e-mail]> wrote:
>
> PR #208 [1] proposes to improve the way kramdown-rfc-extract-sourcecode generates the filenames for sourcecode extracted by it:
>
> > * sourcecode-name values are less heavily mangled; the characters "-" and "." are now allowed (except at the start) and no longer converted into underscores.
> >
> > * unnamed files now have their sourcecode type attached (e.g., if the sourcecode type is abnf, unnamed-123 ➔ unnamed-123.abnf)
> >
> > This update will, unfortunately, be a flag day for those using this feature from Makefiles or includes in the markdown.
> >
> > close #206
>
> I believe this will be a net win for most applications.
>
> But, as mentioned in the PR, it means there will be a flag day (probably in 1.6.44):
> E.g., in draft-ietf-jsonpath-base.md, we’ll have to change:
>
> OLD: {::include sourcecode/abnf/jsonpath_collected_abnf}
> NEW: {::include sourcecode/abnf/jsonpath-collected.abnf}
>
> I apologize for this nuisance; we normally don’t do flag day changes, but it seems expedient to not introduce tedious gating mechanisms for this specific change in a quite young tool.
>
> If you are using kramdown-rfc-extract-sourcecode today and see a problem with this flag day change (or any other problem, of course), please comment to the PR [1].
>
> Grüße, Carsten
>
> [1]: https://github.com/cabo/kramdown-rfc/pull/208
>
> _______________________________________________
> Rfc-markdown mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rfc-markdown



-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF Administration LLC
[e-mail]