Merging cursor changes instead of accepting the suggested deletions?

Discussion
1

So i used cursor for the first time to fairly quickly build a full stack app that required a lot of code massaging but got me a working version within a few hours. I was stoked.

Then as I continued to use cursor to refine things and add features, it began to change working prior code, but being my first time using it, I didn’t realize it.

I had a working API call to google places, that created a database as expected, then after iimproving some of the features, the next time I ran it all the id’s are ‘null’ and instead of having 300 documents in my DB, i have 1 (it kept using the null id to overwrite the existing id).

My question is how to I merge cursors suggestions instead of accepting changes including deletions? I don’t see an option aside from accept or reject. I can always copy and paste, but was wondering if there is a best practice here.

Thanks.

2

Yeah it has a lot of warts under the hood.

I am beginging to think that in the beginning to prevent these thigns - especially as projects get more complex where the bots can no longer hold the projects full context in pre-digitial-cortex - as it loses context way too soon when you get far into a complex (for the bots memory) project…

Its like we need to build much smaller atomic files/functions? so as to keep it from breaking to widely when it does wonkey edits?

3

I’ve been using the chat for editing recently, instead of the Composer. At this point, it’s much more reasonable, lol. It has less of a mind of its own, but is still very helpful.