-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
enhancement: bulk publish migration to v5 #20255
base: v5/main
Are you sure you want to change the base?
Conversation
* chore: migrate bulkDelete to v5 * chore: change findLocales type to accept strings array * fix: docs prettier styles * chore: remove console.log
…into v5/bulk-publish-unpublish
probably someelse (FE) should approve this pr too :) |
}, | ||
} = useDocLayout(); | ||
|
||
const shouldDisplayMainField = mainField != null && mainField !== 'id'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need this variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer to have it because we use twice on the file
* BoldChunk | ||
* -----------------------------------------------------------------------------------------------*/ | ||
|
||
const BoldChunk = (chunks: React.ReactNode) => <Typography fontWeight="bold">{chunks}</Typography>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at the end the chunks prop is the children prop, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I think formatMessage pass chunks as the children
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just two small comments, I still need to test the code
Thanks for the errors @simotae14 ! I discovered a couple of things:
For this last one we can create a ticket because it's a more complicated thing and I think is a v4 error too (I remember something similar in Releases which works the same way) 🤔 |
New changes on fetching entries on opening modal LGTM, thanks!!
Would like to know why don't we use publishedAt value? |
@madhurisandbhor because right now we have two versions of the entry (the published one and the in draft one). We want to use the one in draft (to validate it) and in this version publishedAt is null (because is in draft), but we want the "status" (which takes in consideration all the versions of the entry). Actually this change is interesting, probably we want to discuss it more with Yannis Could you add these two issues you found to the blitz docs? 🙏 |
What does it do?
Bulk Publish action migrated to v5 without any v5 design changes.
Related issue(s)/PR(s)