@Yann-Kerherve Hi Yann,

thanks for fixing this - plugin is now published.

Have a great day!
Pavel

@antflash22 Thanks for your changes and the information. Your plugin is now published.

Thanks for building with Windy!

@antflash22 Thanks for your changes and the information. Your plugin is now published.

Thanks for building with Windy!

Hi @antflash22

• I'm unable to test the plugin, there's an error:

can't access property "start", info is null
radarCalendarChanged plugin.svelte:601

• the onDestroy method should remove all listeners with store.off(), map.off()
• did you know Windy has a weather warnings layer? Did you find any missing data?

Thanks @Xutao-Guo, update published.

@tomA27 If you wish to test multiple versions, you can use the private: true flag in plugin config and remove it in a version ready for release.

You don't have to use it though. Currently we only publish plugins if an update is requested either here or in our Slack channel, so users won't be impacted unless you request.

@tomA27 Many thanks for fixing. Plugin is now published.

It is required to do a new publish pipeline for every update, so you did right.

Hi @tomA27

Just one small issue: the plugin's screenshot won't load because the filename starts with a capital S. Can you please rename it to lowercase "screenshot.png".

Thanks!

@Yann-Kerherve Hi Yann,

thanks for fixing this - plugin is now published.

Have a great day!
Pavel

@Yann-Kerherve Thanks for your plugin. Can you look at the points below please (just quick fixes).

• closing the plugin sidebar with the back arrow doesn't work: bcast is not defined
• update "repository" in your pluginConfig (currently points to Windy template)

Thanks, Pavel

Thank you, @francescogola for your plugin. It's now published.

To address your questions:

• yes, after each update you should run the GitHub action that will notify us. We then review your changes and publish the update.
• there's a newly implemented feature that should notify users there's an update available.

Pavel