Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Basic usage instructions

See original GitHub issue

Not sure where/how yet. But regarding what:

twiddle.json - What to put there/how/what
autorun/reload
…

Issue Analytics

State:
Created 8 years ago
Comments:24 (20 by maintainers)

Top GitHub Comments

1reaction

sheriffderekcommented, Feb 27, 2016

@acorncom An outline of how things work would be helpful to me, being a person who is CLI all the way. I was tempted to build a starting point for a series of example, and I used the CLI folder structure I’m used to / but that doesn’t work. Is it POD structure? Is there a simplified structure that keeps twiddle rad? If so, what is it?

I’d also be interested to know what twiddle doesn’t have yet. For example, can I add an Adapter? Can I use a serializer? Can I pull in data from an external API? What are the limitations? I’ll love it either way, but I wont love wondering what I can and can’t expect.

Saved twiddles are easy to retrieve now as far as I can see, but the list @Gaurav0 was starting was good.

I’d order it based on complexity. Folder structure and Routing and general limitations seem like things I would teach someone very early. Then probably adding other dependencies. Then styles.

0reactions

Gaurav0commented, Aug 1, 2018

relevant: #634