Schema field order not saved
- Dominant language
- Java
- Stars
- 593
- Forks
- 123
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 4
Description
## Gentics Mesh Version, operating system, or hardware.
0.31.4 running in docker-compose https://github.com/gentics/mesh-compose
## Operating System
MacOS 10.14.3 (18D109)
## Problem
On creating or updating Schemas and Microschemas, the order of the ```fields```-Array is not saved.
Instead, the order is determined alphabetically referring to the ```name``` property string of a field.
## Expected Behavior
As specified for the frontend, the user can determine the order of Schema and Microschema fields.
Related to frontend issue: https://github.com/gentics/mesh-ui/issues/122
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing schema and microschema creation or update through the API, then trace where the fields array is persisted or serialized. Done means the submitted field order is retained rather than replaced by alphabetical order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100