-
Notifications
You must be signed in to change notification settings - Fork 32
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
Calendar setting to filter events #1258
Labels
Comments
I've applied a rule: Title starts with "@" -> Import But it's importing all events. I guess the rule is working well but my expectation was that the contrary would not happen ( = if events don't start with "@" don't import). So maybe we should offer another option "Don't start with" to make that explicit? (this is what we need for the first client; I don't know if with the current options we could do it) |
Yes, for the client the setup I was testing is "If title not contains @,
then Ignore", but the @ could be in the middle. I'll add the option.
…On 3 January 2018 at 09:18, Álvaro Ortiz ***@***.***> wrote:
I've applied a rule:
Title starts with "@" -> Import
But it's importing all events. I guess the rule is working well but my
expectation was that the contrary would not happen ( = if events don't
start with "@" don't import). So maybe we should offer another option
"Don't start with" to make that explicit? (this is what we need for the
first client; I don't know if with the current options we could do it)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1258 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABE0KLCR5VU0VhxWZ-yHrQOl1LTMmzsks5tGze4gaJpZM4RAJh3>
.
--
Fernando Blat
twitter.com/ferblape
Populate / Projects for civic engagement
http:https://populate.tools
|
Fix ready and tested in #1296
…On 3 January 2018 at 09:35, Fernando Blat ***@***.***> wrote:
Yes, for the client the setup I was testing is "If title not contains @,
then Ignore", but the @ could be in the middle. I'll add the option.
On 3 January 2018 at 09:18, Álvaro Ortiz ***@***.***> wrote:
> I've applied a rule:
>
> Title starts with "@" -> Import
>
> But it's importing all events. I guess the rule is working well but my
> expectation was that the contrary would not happen ( = if events don't
> start with "@" don't import). So maybe we should offer another option
> "Don't start with" to make that explicit? (this is what we need for the
> first client; I don't know if with the current options we could do it)
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#1258 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABE0KLCR5VU0VhxWZ-yHrQOl1LTMmzsks5tGze4gaJpZM4RAJh3>
> .
>
--
Fernando Blat
twitter.com/ferblape
Populate / Projects for civic engagement
http:https://populate.tools
--
Fernando Blat
twitter.com/ferblape
Populate / Projects for civic engagement
http:https://populate.tools
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to enhance the calendar integration code to allow filtering events that contain a character or a string. For example, import only those events which contain an "@" or those that contain the string "[gobierno]".
The filter, for the moment will be a requisite for the event to be imported, and those events that don't contain that string won't be imported.
The text was updated successfully, but these errors were encountered: