Note: We cant update composer/composer to the newest version
because it is blocked by wp-cli/wp-cli-bundle (composer/composer: ^1.10.23 || ~2.2.17)
[MAILPOET-5633]
In #5145, we started using the same Redux store for all segment pages.
This created an unintended side effect that the error messages displayed
when the user is creating a segment are persisted across the other
different segment pages.
So, for example, if a user tries to create a segment with a name that
alraedy exists and then clicks the back button to go back to the segment
templates or segment listing page, the error message will still be
displayed.
This commit fixes this problem by emptying the error messages before
unloading the page to edit or create segments.
[MAILPOET-5605]
This code was preventing WordPress from rendering the public.js
script as deferred.
The defer attribute can be applied only to scripts
that are loaded via src. WP detected that there was an associated
inline script and removed the defer attribute from the public.js script.
In this commit, I moved the initialization of the error message to public.js and
I pass the value via static object.
[MAILPOET-5623]
A PR was merged to trunk enforcing the use of the kebab case pattern for
file and directory names. This commit changes the name of a directory
and two files that were created before the PR was merged.
[MAILPOET-5398]
This commit changes the layout of the conditions of some segments in the segment
edit page so that they are better displayed in the new design (all the
modified segments contain at least one select box with potential long
optons).
To do that it removes the two remaining Grid.CenteredRow components and also
replaces isFullWidth with isMinWidth for the smaller select boxes in the
same condition.
[MAILPOET-5398]
This commit attempts to fix the design of the segment conditions in the
segment edit page when there are long items in a select box. To do that,
it removes the two remaining Grid.CenteredRow components and also
removes the `dimension='small'` from the `<ReactSelect>` component.
It is only applied to the <EmailClickStatisticsFields> component so that
we can test it and then after expand to the other components if there
are no further changes that we want to make.
[MAILPOET-5398]
Doing this to hopefully workaround the following ESLint error that John
is seeing in his local env
(https://github.com/mailpoet/mailpoet/pull/5174#discussion_r1334663426):
ESLint: Invalid type "any" of template literal expression.(@typescript-eslint/restrict-template-expressions)
[MAILPOET-5398]
