<![CDATA[Making a second fork of windy-plugins on github]]>Hi @ivo and @TomSlavkovsky,

I have an idea for a new plugin, which I've been testing out. But you cannot fork a repository on Github that you've already forked once before.

What would you recommend I do to create a second plugin? I'd rather not have to set up a new Github account just for this... Is it even necessary to use a fork? Or would the npm dependency stuff still work fine if I simply clone it?

Any advice is appreciated!

]]>https://community.windy.com/topic/10185/making-a-second-fork-of-windy-plugins-on-githubRSS for NodeFri, 17 Apr 2026 21:03:47 GMTWed, 13 Nov 2019 07:09:36 GMT60<![CDATA[Reply to Making a second fork of windy-plugins on github on Thu, 21 Nov 2019 08:05:21 GMT]]>Thanks @rittels! Exactly what I needed :)

]]>https://community.windy.com/post/33911https://community.windy.com/post/33911Thu, 21 Nov 2019 08:05:21 GMT<![CDATA[Reply to Making a second fork of windy-plugins on github on Thu, 21 Nov 2019 06:17:30 GMT]]>@johnckealy

hi

from: https://github.com/windycom/windy-plugins/blob/master/docs/WINDY_API.md#module-picker

broadcast.fire('rqstClose', 'picker')

]]>https://community.windy.com/post/33908https://community.windy.com/post/33908Thu, 21 Nov 2019 06:17:30 GMT<![CDATA[Reply to Making a second fork of windy-plugins on github on Thu, 21 Nov 2019 03:31:10 GMT]]>Hi @marekd,

Thanks for the response. My plugin is nearly done. One more question – How do I close the picker in javascript?

The API docs suggest that I should just be able to do

import picker from '@windy/picker, and
picker.close() // (assuming it's been opened)

but this logs the error:
plugin.js:52 Uncaught (in promise) TypeError: picker.close is not a function

if I console.log(picker), it outputs:
{ident: "picker", latestId: 6, _eventedCache: {…}, trigger: ƒ, fire: ƒ}

I just want to keep the picker closed entirely for the plugin, or close it immediately if it does open. Is there a bug in the backend, or am I just missing something?

Thanks,
John

]]>https://community.windy.com/post/33902https://community.windy.com/post/33902Thu, 21 Nov 2019 03:31:10 GMT<![CDATA[Reply to Making a second fork of windy-plugins on github on Thu, 14 Nov 2019 08:52:15 GMT]]>Hi, you do not have to fork the repository. You can clone it and change the origin locally. Or you can just download it as a zip file and init a new git repo.

]]>https://community.windy.com/post/33479https://community.windy.com/post/33479Thu, 14 Nov 2019 08:52:15 GMT