You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ey @ferranpujolcamins,
firstly, I appreciate your suggestions ^^ - thanks for coming to nef and give it a try!
About your suggestion, I agree it is a nice-to-have feature. Currently, I'm working on big refactor to migrate nef to a complete functional architecture using bow+swift. I comment about it because this refactor will help in future features like this one.
After the refactor, nef will provide APIs like
staticfunc render(playgroundsAt:URL,
mainPage:URL,
into output:URL)->IO<nef.Error,NEA<URL>>
Where IO<nef.Error, NEA<URL>> will be:
fails error with type nef.Error
successNEA<URL> list of rendering Playgrounds.
So you can easily call them to regenerate your Jekyll site. On a first review, we should investigate 2 things:
How to subscribe to changes in any folder at mac-filesystem, so reactively we could invoke nef API after for example save any page (or playground)
Let if we could invoke a refresh in the browser to auto-render the new content (prevent cache web-browser...) [maybe Jekyll server does it for us]
On this way, easily we could provide the option you suggest, whereafter any change in your playground it will regenerate your jekyll-site.
While I continue working on the refactor, if you want, you can investigate it... even add this option to jekyll-CLI when the refactor will be completed. (~mid of feb)
wdut?
Of course, when you start to work in the feature, I will provide u with any resource or help you need :)
I usually write my docs on a swift playground while previewing the generated jekyll site in my browser.
I use
jekyll serve
, but I still to runnef jekyll
manually in order for the generated markdown to be updated on a change.I'd love a --watch option so nef automatically regenerates the markdown files for me.
The text was updated successfully, but these errors were encountered: