4 ms·
Yeah, based on the issues that might be a fair assumption: https://github.com/curusarn/resh/issues https://github.com/curusarn/resh/issues more expected issue
by o_____________o 4y ago
Yeah, based on the issues that might be a fair assumption:
https://github.com/curusarn/resh/issues https://github.com/curusarn/resh/issues
more expected issues from relying on a big JSON file:
https://github.com/curusarn/resh/issues/171 https://github.com/curusarn/resh/issues/171
- curusarn 4y agoHi, author here. I have almost two years of history on my machine right now. It's 77k history records which takes up 126MB. The amount of saved context is currently excessive. When I started the project I didn't know exactly what I would need so I included a lot of things that were never used. I do plan to reduce the history records to about 16 fields which should more than halve the space requirements. I haven't done this yet because I need to safely convert the existing history records people already have to the new reduced version during update which is tricky.
- yjftsjthsd-h 4y agoCan you save a version flag and support both until you write the migration logic? That way at least new users benefit