Convert the schema to use a data property to store the serialized settings instead of having one property for each setting

Created on 28 February 2012, over 12 years ago
Updated 26 July 2024, about 1 month ago

Currently the entire schema is full of single value properties (settings) which could actually all be moved into one serialized data property. Is there a reason why every setting currently has its own column? Using a data property for the settings makes a lot of sense if you ask me and it is also way more flexible and could be used by other implementing modules to store additional information to customize specific quizzes, etc.

πŸ“Œ Task
Status

Closed: outdated

Version

5.0

Component

Code - Quiz core

Created by

πŸ‡¦πŸ‡ΉAustria fubhy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    With D7 approaching EOL soon I've started the process of triaging the D7queue here. Since there hasn't been any movement on this going to close out.

Production build 0.71.5 2024