You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The file or directory to be searched for annotations. If a directory, it will be searched recursively. This can be
@@ -68,3 +77,21 @@ Configuring Code Annotations is a pretty simple affair. Here is an example showi
68
77
extensions are turned on here. The key is the extension name, as given in the ``setup.py`` or ``setup.cfg`` of the
69
78
package that installed the extension. The values are a list of file extensions that, when found, will be passed to
70
79
the extension for annotation searching. See :doc:`extensions` for details.
80
+
81
+
``report_template_dir`` (optional)
82
+
When running the ``generate_docs`` comman you can specify a custom template directory here to override the default templates if you would like a different look.
83
+
84
+
``rendered_report_dir`` (optional)
85
+
When running the ``generate_docs`` command, this option specifies the directory where the rendered report will be written. The default is ``annotation_reports`` in the current working directory.
86
+
87
+
``rendered_report_format`` (optional)
88
+
When running the ``generate_docs`` command, this option specifies the format of the rendered report. Options are ``html`` and ``rst``. The default is ``rst``.
89
+
90
+
``rendered_report_source_link_prefix`` (optional)
91
+
When running the ``generate_docs`` command, this option specifies the URL prefix to use when linking to source files in the rendered report. When specified, "local" source files (those not found in site-packages) will be appended to this setting to create hyperlinks to the lines in source files online. For Github links this is the correct format: ``https://github.com/openedx/edx-platform/blob/master/``. The default is an None.
92
+
93
+
``trim_filename_prefixes`` (optional)
94
+
When running the ``generate_docs`` command, this option specifies a list of prefixes to remove from the beginning of filenames in the rendered report. This is useful for making the report more readable by removing long, repetitive prefixes of the type often found in a Django search. The default is an empty list.
95
+
96
+
``third_party_package_location`` (optional)
97
+
When running the ``generate_docs`` command, this option specifies the location of third party packages that may have been found in a Django search. This is used to determine if a file is a third party file or not. The default is ``site-packages``.
Copy file name to clipboardExpand all lines: docs/getting_started.rst
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,3 +126,17 @@ Add more structure to your annotations
126
126
Annotations can be more than simple messages. They can enforce the use of choices from a fixed list, and can be grouped
127
127
to provide more context-aware information. See :doc:`configuration` and :doc:`writing_annotations` for more information
128
128
on how to use those options.
129
+
130
+
Get a human readable report
131
+
---------------------------
132
+
The output generated by the search commands is a YAML file. To get a human readable report generated from one of those files in either rst or html format, you can use the ``generate_docs`` command.
133
+
134
+
There are several configuration options available for this command, including the ability to specify the output format, the output directory, and create links to the source files on sites like Github. For more information, see :doc:`configuration`. Once your configuration is set, you can run:
Which will generate files in the output directory you configured. From there you can open the files in your browser to see the report, if you chose HTML, or use a tool like `restview`_ to render the RST files to your browser.
0 commit comments