quarto-dev / quarto-dev/quarto-cli

`quarto publish confluence` fails to find, or correctly link parent pages.

Aperta
#7,992 7 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

bug publishing-confluence
Lingua principale
JavaScript
Stelle
6k
Fork
458
Merge medio
1g 9h
PR unite (30g)
41

Descrizione

Bug description

I created a git repository to reproduce this issue. Please clone this git repo for a reprex.

It seems that sub pages cannot reference parent pages accurately with the [text](PATH/To/QMD) syntax specifically for quarto publish confluence and when using ../File.qmd or /file.qmd.

It should be noted that this syntax works perfectly when viewing the rendered html pages from RStudio, but otherwise not.

Description of the Project structure

├── index.qmd
├── _quarto.yml
├── README.md
├── reports
│ ├── 2022-01.qmd
│ └── 2022-03.qmd
└── section.qmd

Files and their links:

  1. index.qmd contains 4 links: one link to each of the sub pages and then 2 links to section.qmd.
    • Both of the table links work on confluence 👍
    • [go to section](section.qmd#Challenges and Opportunities) links to the page but not the section 👎 .
    • When copying the link from confluence and manually pasting it (the second link), the following works:
      [New syntax](section.qmd#Challenges-and-Opportunities%5BinlineExtension%5D)
  2. 2022-01.qmd contains 2 links, both trying to reference the top level index.qmd except one using ../index.qmd and the other using /index.qmd. 👎 Does not work but for different reasons.
    • In the ../index.qmd syntax, the link is never created.
    • In the /index.qmd syntax, A link is created but it redirects to the root uri on confluence, i.e. if your confluence site was named site.atlassian.net then /index.qmd syntax creates a link that redirects to https://site.atlassian.net/index.qmd
  3. 2022-03.qmd contains only 1 link, still using ../index.qmd syntax except this file doesn't try and specify a section to jump to, still doesn't work 👎
Steps to reproduce
git@github.com:jtlandis/quarto-confluence-link.git
cd quarto-confluence-link
quarto publish confluence
Expected behavior

No response

Actual behavior

No response

Your environment
  • IDE: RStudio
  • OS: RHEL8
  • Confluence: Cloud
Quarto check output
quarto check


[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.1: OK
      Dart Sass version 1.55.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.3.450
      Path: /usr/local/quarto-1.3.450/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.6.8
      Path: /usr/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

[✓] Checking R installation...........OK
      Version: 4.3.2
      Path: /usr/lib64/R
      LibPaths:
        - /home/justinlandis/R/x86_64-redhat-linux-gnu-library/4.3
        - /usr/lib64/R/library
        - /usr/share/R/library
      knitr: 1.43
      rmarkdown: 2.23

[✓] Checking Knitr engine render......OK

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Clone the linked quarto-confluence-link repository and run quarto publish confluence with the listed index.qmd, section.qmd, and reports pages. Compare the generated Confluence links for parent pages, relative paths, absolute paths, and anchors with the working rendered HTML links. Done means all documented parent-page and section links resolve correctly in Confluence Cloud.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript
Ambito
tooling
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
52/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.