And added a subsection at the end of the forecast section, yes. The changes are minor and it can be that they do such things on purpose, but it is what it is. I keep telling people to make their weather skin regex patterns as flexible as possible, at least for the main site JSON, but apparently folks never learn and believe it's too complicated, prefering to rebuild their skins over and over each time such a change occurs. For example, in my skin, the pattern getting the forecast is stored in a variable which then gets used in the parsing, and was like:QuakeGuy wrote: ↑August 21st, 2020, 3:50 pm What the heck? Today my skin stopped working again. After a investigation of the situation i realized, they only changed the part getSunV3DailyForecastUrlConfig to getSunV3DailyForecastWithHeadersUrlConfig.
I get the feeling they do this small changes on purpose. Anyways, if this is still the case tomorrow i will release a tiny update/fix.
where is just another variable used to store either the unescaped ( ) or escaped ( ) quote, so that I can parse both the main site JSON and the API one using the same regexes. Given the way the patterns are built, no name modification was needed for the change in the forecast section name (it works with both and ) and the only change that was needed to make it work again for the main site JSON was making the number or curly brackets at the end flexible as well (since as I mentioned, they added a new subsection inside the forecast one, which means either less or more brackets here are there), like:
and that was it. But then, I have to admit, my way doesn't suit everyone, of course, first because it requires a bit more advanced knowledge of regex nd secondly because it's tailored to my skin's approach on things.