5 commits

Author	SHA1	Message	Date
Hannah Wolfe	8383b11d84	Cleaned up some weird require paths ... - these require paths go back too far. They work but it's odd!	2020-05-01 18:00:57 +01:00
Daniel Lockyer	d6272eff42	Checked structure of data in routes.yaml ... fixes #11774 - providing data as a list ends up hitting code paths that can't handle arrays - this ends up causing an InternalServerError - this commit checks the input type is an object - spotted in Sentry	2020-04-27 17:39:48 +01:00
Hannah Wolfe	72679aefb9	Updated inconistent frontend debug statements ... - Fixed debug statements had wrong/inconsistent debug statement path after refactor	2019-11-05 15:06:15 +07:00
Nazar Gargol	e10e71cc26	Added /frontend folder to default lint command ... no issue - The folder was overseen to be added to lint rules after it has been extracted out of /server	2019-08-08 10:47:13 +02:00
Naz Gargol	0bf1542bc6	Extracted settings service part manipulating routes.yaml (#10800) ... 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.	2019-06-25 18:33:56 +02:00

Renamed from core/server/services/settings/validate.js (Browse further)