Skip to content

[FW][FIX] developer/rdtraining: comply with the guidelines for report naming #1426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[FW][FIX] developer/rdtraining: comply with the guidelines for report naming #1426

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/developer/howtos/rdtraining/J_reports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ There is no strict rule for the file names or where they are located, but these
typically stored in 2 separate files within a ``report`` folder in the top level of your module's
directory. If a module has many or multiple long report templates, then they are often organized in
a logical manner across different files named after the report(s) they contain. All actions
for the reports are usually stored in the same file ending with ``_report_views.xml`` regardless of the
for the reports are usually stored in the same file ending with ``_reports.xml`` regardless of the
number of reports it contains.

Therefore it is expected that your work tree will look something like:
Expand All @@ -47,8 +47,8 @@ Therefore it is expected that your work tree will look something like:
│ ├── *.py
│ └── __init__.py
├── report
│ ├── estate_report_templates.xml
│ └── estate_report_views.xml
│ ├── estate_property_templates.xml
│ └── estate_property_reports.xml
├── security
│ └── ir.model.access.csv
├── views
Expand Down