- Status changed to Postponed
8 months ago 8:56pm 18 April 2024 - 🇮🇹Italy lussoluca Italy
A solution can be to add a new tab and save the schema metadata in a third-party setting of the backend configuration, but at this point, I think this is no longer a priority for the first release.
I've added a message to the "Fields" tab that warns the user to go to the "Processor" tab to complete the setup.
- Status changed to Active
6 months ago 9:25am 9 July 2024 - Merge request !27Issue #3208173: Move schema settings into a new tab → (Merged) created by lussoluca
- First commit to issue fork.
-
lussoluca →
committed 82d7cc47 on 1.0.x
Issue #3208173 by lussoluca, luxx91: Move schema settings into a new tab
-
lussoluca →
committed 82d7cc47 on 1.0.x
- Status changed to Fixed
5 months ago 9:04am 17 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.