Odoo
Sublime text syntax highlighting for QWeb templates, OWL templates and views.
Details
Installs
- Total 5
- Win 0
- Mac 0
- Linux 5
| Aug 9 | Aug 8 | Aug 7 | Aug 6 | Aug 5 | Aug 4 | Aug 3 | Aug 2 | Aug 1 | Jul 31 | Jul 30 | Jul 29 | Jul 28 | Jul 27 | Jul 26 | Jul 25 | Jul 24 | Jul 23 | Jul 22 | Jul 21 | Jul 20 | Jul 19 | Jul 18 | Jul 17 | Jul 16 | Jul 15 | Jul 14 | Jul 13 | Jul 12 | Jul 11 | Jul 10 | Jul 9 | Jul 8 | Jul 7 | Jul 6 | Jul 5 | Jul 4 | Jul 3 | Jul 2 | Jul 1 | Jun 30 | Jun 29 | Jun 28 | Jun 27 | Jun 26 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Linux | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Sublime - Odoo
Snippets
Add some snippets for common code - new model - overwrite a model - views (form, list, kanban, search, etc) - common methods (create, write, etc)
Check the snippet folder to see what's available.
Syntax highlighting
Syntax highlighting for QWeb templates, OWL templates, views, and access CSV files.
Choose “XML - Odoo”, and it will automatically choose the right syntax
- OWL syntax (with JS in expression) if inside <templates/>
- View syntax (with python in expression) if inside <odoo/>
It highlight JS template inside Python template (eg template of kanban views)
It also highlight mail templates and “backend” templates.
And ir.model.access.csv
With this syntax highlighting comes the symbols, you can jump to view / component template with ctrl+r / ctrl+shift+r
Go To Definition
You can configure key bind to make “go to definition” work in views / OWL components (it uses sublime text symbols indexes, and so many results can be returned, they are sorted with a heuristic, similar filenames are displayed first).
// Standard sublime text `goto_definition`
{ "keys": ["primary+d"], "command": "goto_definition" },
// When the LSP has the feature
{
"keys": ["primary+d"],
"command": "lsp_symbol_definition",
"context": [
{ "key": "lsp.session_with_capability", "operand": "definitionProvider" },
{ "key": "auto_complete_visible", "operand": false }
]
},
// Custom Odoo "Go To Definition"
{
"keys": ["primary+d"],
"command": "goto_definition_odoo_xml",
"context": [{ "key": "selector", "operator": "equal", "operand": "text.xml.odoo-view, text.xml.owl, text.xml.odoo" }]
},
Same for goto_reference.
“json
{ "keys”: [“primary+shift+r”], “command”: “goto_reference” },
{
“keys”: [“primary+shift+r”],
“command”: “goto_reference_odoo_xml”,
“context”: [{ “key”: “selector”, “operator”: “equal”, “operand”: “text.xml.odoo-view, text.xml.owl, text.xml.odoo” }]
},
<p align="center">
<img src="img/go_to_definition_1.png">
</p>
<p align="center">
<img src="img/go_to_definition_2.png">
</p>
<p align="center">
<img src="img/go_to_definition_3.png">
</p>
<p align="center">
<img src="img/go_to_definition_4.png">
</p>
<p align="center">
<img src="img/go_to_definition_5.png">
</p>
<p align="center">
<img src="img/go_to_references.png">
</p>
## Commands
Please install [ripgrep](https://github.com/BurntSushi/ripgrep) to use most of commands (they are use instead of slow python code to get the list of modules, list of models, etc)
> sudo apt install ripgrep
You can automatically create Python inherit, JS component, search a view and overwrite it, etc
<p align="center">
<img src="img/demo_view.gif">
</p>
Type "Odoo" in the command palette to see what's available.
> https://youtu.be/lkYhHB83vJ8
## Auto-complete
<p align="center">
<img src="img/demo_env.gif">
</p>
## TODO
- find a way to automatically change `__manifest__.py` without reformatting
- automatically insert the python import at the right place