5715aa2155
closes #11085 - Ghost has been using YAML format for other configurations (e.g. routes). The plan is to move to this format for all user-edited settings files. By default JSON format is still used in Ghost Admin API v2/v3, but will be changed to YAML in API v4. Check referenced issue for more context. - New format supports all the features available before. The main noticeable change is the structure of config file. It is now grouped by redirect HTTP code instead of specifying `"permanent": true | false` attribute for each config property. Example format for YAML config: ``` 302: /from-url/: /to-url/ 301: /category/([a-z0-9\-]+)/i: /tag/$1/ /v([0-9\.]+)/docs/([a-z0-9\-]+)/i: /docs/$2/ ``` - Added 2 new endpoints: `POST redirects/upload` and `GET redirects/download`. These serve as an alias to current GET/POST `/redirects/json. "upload/download" naming pattern is introduced to match the convention with other resources that can be uploaded and downloaded (images, themes etc.). `/redirects/json` endpoints will be removed in Admin API v4 - The parsing code from `custom-redirects.js` has been moved to `frontend/services/redirects/settings.js`. This location is more appropriate for this logic and eventually `custom-redirects.js` middlewear might be moved into "frontend" as this middlewear plays a role mostly effecting that area. |
||
|---|---|---|
| .. | ||
| serializers | ||
| utils | ||
| validators | ||
| frame.js | ||
| headers.js | ||
| http.js | ||
| index.js | ||
| pipeline.js | ||