Skip to content

Commit fc66699

Browse files
committed
AP-25050-register_debug_knime_yaml
1 parent f33a3c8 commit fc66699

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,13 @@ The code is organized as follows:
1818
├── icons
1919
│ └── icon.png
2020
├── src
21-
── __init.py__
21+
── __init.py__
2222
│ └── extension.py
2323
├── demos
2424
│ └── demo-chemistry-python-adapter.knwf
2525
├── tests
2626
│ ├── test
27-
── conftest.py
27+
── conftest.py
2828
│ └── test_extension.py
2929
├── knime.yml
3030
├── pixi.toml
@@ -63,7 +63,7 @@ You can find general instructions on how to work with our code or develop python
6363
```
6464
pixi run register_debug_in_knime
6565
```
66-
Previously this step required modifying the `config.yml`and `knime.ini` files manually. This improvement will allow you to select your KNINE Analytics Platform installation and append the `-Dknime.python.extension.config=<path/to/your/config.yml>` argument automatically to the according `knime.ini` file. You can now test your extension in the KNIME Analytics Platform (e.g. demo workflow).
66+
Previously this step required modifying the `config.yml`and `knime.ini` files manually. This improvement will allow you to select your KNIME Analytics Platform installation and append the `-Dknime.python.extension.debug_knime_yaml_list=<path/to/your/knime.yml>` argument automatically to the according `knime.ini` file. You can now test your extension in the KNIME Analytics Platform (e.g. demo workflow).
6767
7. **Bundle** your extension:
6868
```bash
6969
pixi run build

0 commit comments

Comments
 (0)