gentics / gentics/mesh

Renaming schema/microschema does not update allows in field definitions

Open
#433 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
593
Forks
123
Avg merge
2d 18h
Merged PRs (30d)
4

Description

## Gentics Mesh Version, operating system, or hardware.
- v0.21.1

## Problem
When renaming a schema or microschema, the allow property of all schema field definitions are not updated accordingly. This leads to fields that allow adding nodes of non-existing schemas which messes up the Mesh-UI.

## Reproducer
1. Create this schema:
```json
{
"name": "test",
"fields": [
{
"name": "ref",
"type": "node",
"allow": [
"folder"
]
}
]
}
```

2. Rename the folder schema

## Expected behaviour and actual behaviour
I expected the name of the allowed schema to be changed as well. Currently this does not happen.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by creating the schema from the example and renaming the folder schema, then inspect the schema and microschema rename handling alongside field definitions' allow values. Done means renaming a schema updates every affected allow reference so no field points to a nonexistent schema.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.