feature/api-settings-export-fixes

[55]

Closes #1385

[brylie]

There are still some issues with the i18n keys, so please observe how other i18n keys are structured.

Also, make use of nesting to improve readability. Add a newline after HTML tags, so that child elements are indented one level.

[55]

@brylie added suggested changes.

[brylie]

Small detail, but the word 'backend' was removed on purpose, please revert -- and if possible, remove Backend from the template name too.

Basically, the word 'backend' is appearing in our code quite a lot, and is not really helping improve readability. We have been removing 'backend' and 'frontend' from our user interface and code, to the extent possible.

I can remove the 'backend' from viewApiBackend and all related i18n strings, if you will just clean up this part of the code.

[brylie]

This is really close.

One thing I have been trying to do is remove 'backend' from our code and user interface. It was used in a confusing manner for both end users and developers. We are switching to the following terminology for simplicity:

• API - an API somewhere on the web, added to our catalogue
• Proxy - an API Proxy solution, such as API Umbrella
• ProxyBackend - an API that has been configured behind a proxy, hence 'backend'

We are only using 'backend' related to the third case, in order to distinguish it from a regular API, and to make it easier to describe our software.

[brylie]

I can make the above change, but it is important that we all know to limit the word 'backend'.

[55]

@brylie, got it, thanks for the explanation.

[brylie]

@NNN I made the changes, renaming API related templates for consistency.

[brylie]

@NNN please review.