happy-kitchen-89482
04/14/2024, 5:10 PM-["foo"] syntax) is intended to override any attempt to re-add the item at a higher precedence (e.g., if removed in an env var, you cannot add it back via a CLI flag, you have to overwrite the entire list value via CLI flag to reintroduce the removed value). These tests show that this is deliberate, as does the implementation. Can anyone remember/hypothesize why this is so?happy-kitchen-89482
04/14/2024, 5:11 PMhappy-kitchen-89482
04/14/2024, 5:12 PMhappy-kitchen-89482
04/14/2024, 5:12 PMhappy-kitchen-89482
04/14/2024, 5:12 PMbroad-processor-92400
04/15/2024, 1:15 AM- as a "I really don't want this to appear, no matter what"?happy-kitchen-89482
04/15/2024, 1:50 AMhappy-kitchen-89482
04/15/2024, 1:50 AMhappy-kitchen-89482
04/15/2024, 2:27 AMbroad-processor-92400
04/15/2024, 2:33 AMhappy-kitchen-89482
04/15/2024, 3:42 PMproud-dentist-22844
04/15/2024, 6:28 PM^["foo"]? (where ^ is the regex character negation [^...] )? or maybe: +[^"foo"] or +[-"foo"] so that the + respects precedence?proud-dentist-22844
04/15/2024, 6:33 PM- inside the brackets becomes ambiguous (drop the 4, or add a negative 4): +[-4], so it would probably need to be the carat: +[^4] ...proud-dentist-22844
04/15/2024, 6:34 PM!? +[!4] or +[!"foo"]happy-kitchen-89482
04/15/2024, 11:08 PMhappy-kitchen-89482
04/15/2024, 11:08 PM