-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-03-19] [Violations] Implement violations for mutiple tag lists #37117
Comments
@cead22 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
WIP. I'll have a PR up this week |
Draft PR is up |
PR updated, and should be ready for review early next week |
PR submitted for review |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
This was done but surfaced another bug #38044, and I found the issue. Let's continue the work there |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.50-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-03-19. 🎊 |
Missing $tagLisName
(eg,Missing Department
) violation, isn't represented with amissingTag
violation, but with asomeTagLevelsRequired
with a data object containingerrorIndexes
for the tags that are missing. I didn't see any functionality around that in the PR linked aboveMulti tag file for tests multitags.csv
The text was updated successfully, but these errors were encountered: