Urban Suppiger
Urban Suppiger
This is an alternative POC for leveraging json data: - keeps ContentNode subclasses, but changes to Single Table Inheritance (thus avoiding all the extra joins for every subclass) - still...
DoctrineExtension/Sortable triggers an error when rootContentNode is configured with orphanRemoval:true ```php #[ORM\OneToOne(targetEntity: ColumnLayout::class, cascade: ['persist'], orphanRemoval: true)] #[ORM\JoinColumn(nullable: false, unique: true)] public ?ColumnLayout $rootContentNode = null; ``` Bug is registered...
Da wir das vermutlich noch oft brauchen werden: Gibt es eine Möglichkeit, das als globale #$def irgendwo in den JSON Schema Checker einzubauen? Oder geht das nicht weils ein Key...
Hätten wir hier irgendwie die Möglichkeit, auch mal JsonPatch zu implementieren, und dann je nach ContentType im Request eine andere Merge-Strategie zu verwenden? Bei dieser Frage bekomme ich irgendwie das...
Since #2825: Besides normal field names, this property also accepts nested json paths (anything parseable by lodash get()/set() method). Hence, `path` would be a better name instead of `fieldname`
Unit test for mergePatch function introduced in #2825
## Requirements - Handle page break reasonably - Links should be working (ToC) - Features in Future - Good UX - Perfomance on mobile - Not to many tech stacks...
# Code branches See linked pull requests for timing measurements. - [Baseline](https://github.com/usu/ecamp3/pull/6) Implemented: - Add some missing indexes + add performance measurement via frontend - [Option 1](https://github.com/usu/ecamp3/pull/7) Implemented: - rootContentNode...
- Avoid class/table inheritance - One ContentNode class, structured as proper tree (as-is now) or as nested set (feasability to be evaluated) - `contentType` property defines the type (as-is today)...