[GitHub] mik-laj commented on issue #4588: [AIRFLOW-XXX] Docs improvements

[GitBox <gi...@apache.org>]

mik-laj commented on issue #4588: [AIRFLOW-XXX] Docs improvements
URL: https://github.com/apache/airflow/pull/4588#issuecomment-457756724
 
 
   List of current warning: 
   ````
   1. ../CHANGELOG.txt:944: WARNING: Inline strong start-string without end-string.
   2. ../CHANGELOG.txt:2170: WARNING: Inline emphasis start-string without end-string.
   3. ../CHANGELOG.txt:2170: WARNING: Inline strong start-string without end-string.
   4. /workspace/docs/code.rst:326: WARNING: Inline literal start-string without end-string.
   5. /workspace/docs/code.rst:330: WARNING: Inline literal start-string without end-string.
   6. WARNING: autodoc: failed to import class 'mesos_executor.MesosExecutor' from module 'airflow.contrib.executors'; the following exception was raised:
   cannot import name 'LoginMixin'
   7. /workspace/docs/howto/operator.rst:19: WARNING: Duplicate explicit target name: "google cloud functions api documentation".
   8. /workspace/docs/integration.rst:188: WARNING: undefined label: azurecosmosinsertdocumentoperator (if the link has no caption the label must precede a section header)
   9. /workspace/docs/integration.rst:189: WARNING: undefined label: azurecosmosdocumentsensor (if the link has no caption the label must precede a section header)
   10. WARNING: html_static_path entry '/workspace/docs/_static' does not exist
   ````
   Warnings with numbers 1 to 3 must be repaired in a separate PR. (Discussion: https://github.com/apache/airflow/pull/4588#discussion_r251004599). I do not plan to fix it for this reason in this PR.
   Warning with numbers 4 to 5 I do not understand the reason why this message occurs. I would like to fix it, but if someone helps me, I will be happy.
   Warning with numbers 6. This is a code problem that does not work. Because of this warning, our friend today wrote a message on the dev of the future of Mesos (Discussion: https://lists.apache.org/list.html?dev@airflow.apache.org). I do not plan to fix it for this reason.
   Warning with numbers 7 to 9. I plan to fix it when I find the moments. I have not found the reason for these warning yet. I would be happy if someone looked at it.
   
   Warning with number 10. I did not look at him. 
   There is still a warning with number 11, but it is not displayed. It is possible that when we correct the previous one, it will repair itself.
   
   In my opinion, the change should be merged. The changes are completely independent of each other. Small steps forward. Yesterday no one thought to check the documentation automatically.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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