Webapp template description does not match with files generated

[aranega]

When the webapp template is used, the backend directory is not generated.

Running:

harness-application webapp-example -t webapp

Generates the following files tree:

webapp-example
├── api
│   ├── config.json
│   └── openapi.yaml
├── backend
│   └── webapp_example
│       └── __main__.py
├── deploy
│   └── values.yaml
├── Dockerfile
├── frontend
│   ├── build.yaml
│   ├── package.json
│   ├── package-lock.json
│   ├── README.md
│   ├── src
│   │   ├── App.tsx
│   │   ├── assets
│   │   │   └── icon.png
│   │   ├── components
│   │   │   └── RestTest.tsx
│   │   ├── index.ejs
│   │   ├── index.tsx
│   │   ├── rest
│   │   │   ├── api.ts
│   │   │   ├── base.ts
│   │   │   ├── common.ts
│   │   │   ├── configuration.ts
│   │   │   ├── git_push.sh
│   │   │   └── index.ts
│   │   ├── styles
│   │   │   └── style.less
│   │   └── utils
│   │       └── history.js
│   ├── tsconfig.json
│   ├── webpack.config.dev.js
│   └── webpack.config.js
├── README.md
└── test
    ├── api
    │   └── test_st.py
    └── e2e
        └── landing.spec.ts

We can see that the backend folder only contains a directory with a __main__.py file in it.

However harness-application --help mentions that:

- webapp (webapp including backend and frontend).

[zsinnema]

@aranega this seems correct behaviour to me. You should specify the backend type: Flask or Django

[aranega]

Ah, ok :), sorry for the issue @zsinnema !
The thing then is that harness-application --help is confusing as it yields: - webapp (webapp including backend and frontend).

[afonsobspinto]

I'm reopening the issue after re-framing it with @aranega's last comment information

[filippomc]

Agree the command help and the docs should mention this, otherwise it's not really working as expected by the user