Default calendar customEvents not working

[sdetweil]

@pauabaer you didn’t add the debug setting to config.js

the transform happens in the front end, the backend (node_helper) gets the events from source and formats them for frontend.tye log you showed is from the backend

[pauabaer]

@sdetweil
I did add the debug setting but presumably at the wrong position.
Thought I should add it here:

module: "calendar",
header: "Familienkalender",
position: "top_left",
                   config:{
                          loglevel: ["DEBUG"],
                                        customEvents: [
                                                {
                                                keyword: "Geburtstag",
                                                symbol: "birthday-cake",
                                                transform: {
                                                        search: "^([^\']*) \'(\\d{4})$",
                                                        replace: "$1 ($2)",
                                                        yearmatchgroup: 2
                                                        }
                                                }

[sdetweil]

@pauabaer logevel is above the modules list
its not a module setting

[pauabaer]

@sdetweil
Meanwhile I found the right place. Sorry for this.
In the pic below you can see the entry.

Does help you?

[sdetweil]

your search regex is wrong,

^(.+) (\\d{4}) Geburtstag$

its captures EVERYTHING from the start… and there is nothing left for the remainder of the expression

you need to capture any character UP to the 1st space,

^([^\s]+) (\d{4}) Gerburstag$

I use https://regex101.com/ to test (see below)

escape the backslash as required

[pauabaer]

@sdetweil
Ok. Within the regex101 there is no mistake. But when I change within the config nothing happens again.

[sdetweil]

@pauabaer you needed to escape the \ with another backslash
in the string… its a javascript thing

as I noted in my prior post
also remove the leading /

[pauabaer]

@sdetweil
I did. But…

I got the feeling i am not far away from the solution. Have still patient to bring me to that point? :)

[sdetweil]

@pauabaer do you still see the same error in the dev console?

[pauabaer]