Skip to content
This repository has been archived by the owner on Feb 20, 2022. It is now read-only.

re-run the generator #1

Closed
geoffreydhuyvetters opened this issue Nov 17, 2016 · 6 comments
Closed

re-run the generator #1

geoffreydhuyvetters opened this issue Nov 17, 2016 · 6 comments

Comments

@geoffreydhuyvetters
Copy link

There was a breaking bug in one of the previous version
I think it's a good idea to update your generator and re-run it.

@thibmaek
Copy link
Owner

Thanks for the notice will update it later today. Luckily not publishes on npm registry yet 😅

@thibmaek
Copy link
Owner

thibmaek commented Nov 17, 2016

@duivvv Updated generator, generated a new generator and diffed it against the current generator where I then replaced the lines that had to be replaced.

Can you doublecheck if I fixed it in 478a973 and 3943841 ?

@geoffreydhuyvetters
Copy link
Author

think so, but I'm working on (another) more silent scripts attempt..
too much data flowing in the CLI now

@thibmaek
Copy link
Owner

I'll keep an eye open on the generator ;)
Will close this for now.

@geoffreydhuyvetters
Copy link
Author

@thibmaek
Copy link
Owner

@duivvv thanks ;) was actually just looking at the most recent commits and will add this to 0.1.1 milestone

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants