You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/11/13 21:19:00 UTC
[GitHub] [arrow] toddfarmer opened a new issue, #14628: MIGRATION: Handle Jira auto-numbered ordered list syntax
toddfarmer opened a new issue, #14628:
URL: https://github.com/apache/arrow/issues/14628
[This sample issue](https://github.com/toddfarmer/test_import/issues/268) demonstrates a gap in the jira2markdown syntax conversion utility, which apparently does not recognize Jira's auto-numbered ordered list syntax. This results in it being left as-is, which then renders as markdown headers instead. This probably needs to be fixed before migration.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] toddfarmer commented on issue #14628: MIGRATION: Handle Jira auto-numbered ordered list syntax
Posted by GitBox <gi...@apache.org>.
toddfarmer commented on issue #14628:
URL: https://github.com/apache/arrow/issues/14628#issuecomment-1313782962
Markdown's automatic ordered list syntax is `1. ` rather than `# `. For example:
```
1. Test
1. Test again
1. Third test
```
is rendered as:
1. Test
1. Test again
1. Third test
Because jira2markdown will also convert Jira header syntax (`h1. `, `h2. `, etc.) to markdown header syntax (`# `, `## `, etc.), any conversion from ordered list syntax needs to be done in a manner to avoid conversion of proper headers to ordered list syntax.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on issue #14628: MIGRATION: Handle Jira auto-numbered ordered list syntax
Posted by GitBox <gi...@apache.org>.
jorisvandenbossche commented on issue #14628:
URL: https://github.com/apache/arrow/issues/14628#issuecomment-1313855926
Which jira2markdown implementation are you using? Is this something we could try to fix there?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] toddfarmer commented on issue #14628: MIGRATION: Handle Jira auto-numbered ordered list syntax
Posted by GitBox <gi...@apache.org>.
toddfarmer commented on issue #14628:
URL: https://github.com/apache/arrow/issues/14628#issuecomment-1313860941
It appears that jira2markdown does support this conversion, but is confused by leading spaces before the ordered list identifiers present in the sample issue:
```
# POC ...
# The language ...
```
instead of:
```
# POC ...
# The language ...
```
The latter converts as expected, while the former is left untouched. I suspect the trigger is uncommon in ARROW tickets, but can be identified and fixed prior to migration relatively easily. I may also report as an issue jira2markdown.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org