jsonnet helper for filter creation about gmailctl HOT 3 CLOSED

I don't know how many people would like to see something like this in the common library, but I know what you can do to get there, if you want:

1. You write a proposal with goals and some implementation details.
2. Minimal working implementation.
3. Add a decently documented version to the repo as a contribution (something people can download separately).
4. Make it available in the standard library if adoption justifies it.

I think that especially 1. is important. What are you trying to achieve with this? Less typing? More clarity? In which way would this be advantageous? What is the disadvantage of not having this?

Point 4. also depends in how much other people like this.

Disclaimer: I'm not a Jsonnet guru either. One question that comes to mind however is: how do you see nested filters working? How would something like and(or(not(A), B), C) be represented with your helpers?

As an aside, I was thinking to add some shortcuts that I saw people using in the wild quite a few times. Example:

local lists(ls) = {
  or: [{ list: x } for x in ls],
};

// usage
{
  filter: lists(['[email protected]', '[email protected]']),
  actions: { archive: true },
}

Thanks for your contributions!

from gmailctl.

This issue is stale because it has been open for 30 days without activity.
This will be closed in 7 days, unless you add the 'lifecycle/keep-alive' label or comment.

from gmailctl.

Well, I think the bot made me look at this again.. Sorry never answered and thank you for the detailed response.
I think you got me on the first questions so if I ever get back to improve my gmailctl definitions I might get back to analyze this idea...

from gmailctl.