You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/12/11 08:57:44 UTC

[GitHub] [pulsar] Anonymitaet opened a new issue #5839: [Doc] Fix variable issues

Anonymitaet opened a new issue #5839: [Doc] Fix variable issues
URL: https://github.com/apache/pulsar/issues/5839
 
 
   ### Issue
   
   Currently, for different contents, we use the same variables in multiple versions.
   
   ### Incorrect example 1
   
   When I resolve https://github.com/apache/pulsar/issues/4053, I find that:
   
   **From `2.1.0-incubating` to `2.4.2`, the download links for the contents in the red box are redirected to **2.4.1 links****, which are the **latest version of docs** now (2.4.2 is released, but the docs are not shown on Pulsar website now, so 2.4.1 is the latest).
   
   ![image](https://user-images.githubusercontent.com/50226895/70599960-775c5c80-1c29-11ea-94ea-95de1c52078e.png)
   
   Then I open the original file (that is `client-libraries-cpp.md`) and find that all version docs are using the same variables:
   
   ![image](https://user-images.githubusercontent.com/50226895/70606263-0de34a80-1c37-11ea-8a90-3f0b3e6c2e26.png)
   
   P.S. I search `{{pulsar:rpm:client}}` in Pulsar project, except in `.md` and `html` files, it appears in the`site2/website/scripts/replace.js` file, which contains many variables:
   
   ![image](https://user-images.githubusercontent.com/50226895/70600541-e25a6300-1c2a-11ea-9115-1179b39d1806.png)
   
   ### Incorrect example 2
   
   Taking 2.3.1 as an example, as same to other version docs, it uses a general variable so that it is shown and redirected to 2.4.1:
   
   ![image](https://user-images.githubusercontent.com/50226895/70605953-6bc36280-1c36-11ea-9c8f-a1f72b750526.png)
   
   ### Summary
   
   For different contents, it seems that we can not use the same variables in multiple versions, because each version should have its own specific links.
   
   But I do not know how to change it (seems it needs coding updates?), anyone can help?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services