Skip to content

Refactor how service bodies are stored in configuration. Previously, … - #264

Draft
otrok7 wants to merge 4 commits into
mainfrom
Refactor-how-service-bodies-are-stored-in-configuration
Draft

otrok7 wants to merge 4 commits into
mainfrom
Refactor-how-service-bodies-are-stored-in-configuration

Conversation

@otrok7

@otrok7 otrok7 commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

…the service bodies were stored in the options table as an array of strings, each containing fields of the service body in a comma separated string. This made a bit of sense in earlier version, where the string appeared in the admin UI, but even this has been removed. This was not only inefficient and bad style, but also could lead to missing updates when the name of the service body was modified. Now, we just store the service body id.

…the service bodies were stored in the options table as an array of arrays. Now, they are stored as an associative array with the service body ID as the key and the service body data as the value. This change allows for easier access to service body data by ID and improves performance when retrieving service body information.
@otrok7
otrok7 marked this pull request as draft October 27, 2026 14:16
@github-actions

Copy link
Copy Markdown

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.


🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

@otrok7 otrok7 self-assigned this Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant