Thomas Heartman b5de65bb8e chore: wait to input the name of the segment when checking for error messages (#7377) ... This change adds a wait statement before entering the name of the segment when checking for error messages that this segment name already exists. This is the same workaround that we did in https://github.com/Unleash/unleash/pull/7289, which seems to have worked. Like in that PR, using waits is still an antipattern, but it appears to be working. Maybe it’s time to look more deeply at why it happens? Why isn’t the field ready to receive input even though it’s on the page? Is it mui’s fault or ours?		2024-06-12 14:06:44 +02:00
..
demo
feature	chore: make feature.spec and segements.spec more resilient (#7289)	2024-06-07 08:37:53 +02:00
groups
projects	feat: rename toggle to flag with db migration (#7118)	2024-05-23 10:17:02 +03:00
segments	chore: wait to input the name of the segment when checking for error messages (#7377)	2024-06-12 14:06:44 +02:00