Isi Robayna

@rkkandah Thanks you for the PR, any chance you could also add some specs for this document? Typically you would add a good / bad fixture among other things.

@RomanKapitonov WOW, this is fantastic! This will be one of those key features will be very handy to have. I have to take a deeper dive and study your PR...

@RomanKapitonov Thank you! very good info @kputnam What do you think?

@RomanKapitonov Thanks Roman, a mountain of very valuable data to look at. Definitely room for improvement.

Interesting findings, in particular, memory usage. Could be a case where speed might become irrelevant for the sake of keeping memory low. BTW, I thought `unshift` was supposed to be...

Don't we still need a segment on line 36 even for ```Stupidedi::Zipper::RootCursor``` so later on ```critique``` can be called? ```FailureState.mksegment(segment_tok, state)``` which is define as: ```ruby def mksegment(segment_tok, parent) segment_val...

Adding this logic to Line 36 (generation.rb) ```ruby if zipper.class == Stupidedi::Zipper::RootCursor active

This item will make the library even better, a step in the right direction. Nothing wrong with having clear guidelines hence `repatable_detail` and `non-repeatable` concept for tables makes sense to...

same issue with latest version. Using ```nuxt.js``` also created a plugin as it seems to be the prefered way of consuming components but does not work (other components do work...

Any updates on this pull?