You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the shouldPublish option when calling setTagsForEntries should result in the same behavior as when setting the shouldPublish options when calling transformEntries.
Actual Behavior
shouldPublish is unsupported.
If using TypeScript, we get this message, which makes sense.
Object literal may only specify known properties, and 'shouldPublish' does not exist in type 'ISetTagsForEntriesConfig'
If we run the migration anyway, the option is ignored.
Possible Solution
Support shouldPublish as an option when calling setTagsForEntries.
Or maybe it's better to be able to set tags and fields with the same migration function.
Steps to Reproduce
Set the shouldPublish option when calling setTagsForEntries.
Context
We sometimes only migrate tags.
Environment
Package Version: 4.14.1
The text was updated successfully, but these errors were encountered:
I'd love to see the shouldPublish option (with default 'preserve') for setTagsForEntries.
We use tags for internationalisation, so every time a new country is added we need to update nearly 1300 entries with the new tag. Adding the tag works perfectly with setTagsForEntries but publishing 1300 pages in batches of 40 afterwards is very time consuming
Expected Behavior
Setting the
shouldPublish
option when callingsetTagsForEntries
should result in the same behavior as when setting theshouldPublish
options when callingtransformEntries
.Actual Behavior
shouldPublish
is unsupported.If using TypeScript, we get this message, which makes sense.
If we run the migration anyway, the option is ignored.
Possible Solution
Support
shouldPublish
as an option when callingsetTagsForEntries
.Or maybe it's better to be able to set tags and fields with the same migration function.
Steps to Reproduce
Set the
shouldPublish
option when callingsetTagsForEntries
.Context
We sometimes only migrate tags.
Environment
The text was updated successfully, but these errors were encountered: