-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added migration and schema change for posts_meta.hide_title_and_feature_image
#17187
Added migration and schema change for posts_meta.hide_title_and_feature_image
#17187
Conversation
It looks like this PR contains a migration 👀 General requirements
Schema changes
Data changes
|
40996cd
to
5740a12
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #17187 +/- ##
==========================================
+ Coverage 71.70% 71.76% +0.05%
==========================================
Files 1836 1836
Lines 116454 116462 +8
Branches 17275 17298 +23
==========================================
+ Hits 83508 83579 +71
+ Misses 31829 31762 -67
- Partials 1117 1121 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
…ure_image` closes TryGhost/Product#3550 We want to allow an option to hide the title and feature image on a per-page basis, to do that we need somewhere to store the setting value. The existing `posts_meta` table is the simplest candidate, especially as this is a single setting and we don't have a desire to introduce many such settings. - added migration that adds the `hide_title_and_feature_image` column to the `posts_meta` table with a `boolean` data type and a default value of `false` (matches behaviour of all existing pages) - updated schema file for initial database creation
5740a12
to
ceae2e2
Compare
Full API implementation on top of this data change can be seen in 59d5223 |
closes https://github.com/TryGhost/Team/issues/3550
We want to allow an option to hide the title and feature image on a per-page basis, to do that we need somewhere to store the setting value. The existing
posts_meta
table is the simplest candidate, especially as this is a single setting and we don't have a desire to introduce many such settings.hide_title_and_feature_image
column to theposts_meta
table with aboolean
data type and a default value offalse
(matches behaviour of all existing pages)