0bf1542bc6
refs #10790 refs #9528 - The settings service was designed to handle more settings then just routing, but till this day there wasn't anything else added. As routes.yaml is only being used by frontend router so conceptually it fits better to have this code in frontend, so that it doesn't have to reach out to server - The code left in server settings is the one that interacts with the database `settings` table and only partially provides information to frontend. That part is known as 'settings cache' and will be accessed through API controllers. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| mocks | ||
| api.js | ||
| assertions.js | ||
| configUtils.js | ||
| index.js | ||
| urlUtils.js | ||