Ok I got a first cut of Ruby parser in - the latest commit on Rails was a little sluggish but it works!
Right now the parser intentionally tags modules as classes, we made some assumptions in the generic parser code for other languages that don't quite align with ruby's notion of modules, but that'll be adjusted in the near future.
hey this is awesome. I'm using it and I think it's got some wheels. But please add a quick link to submit feedback in app!
Here's what I got so far:
- specific issue: I updated the triage text before submitting to the planning stage. Although the triage text maintained my edits I'm pretty sure the prompt that went into the first Plan generation did not include my edits.
- rough idea: Plans are long and take awhile to regenerate. There's fear of submitting for a regeneration when all you want is it to understand something different about the high level thoughts. Maybe keeping a history of plans or even diffing them could be useful.
Both items above coalesce into a desire to 'rewind' back to the top of the process and try to get the context understood at the beginning, and have that clearly reflected to the user so that as you move through to details it gets easier to handle the nitty gritty without as much editing.
ivanovm|1 year ago
Right now the parser intentionally tags modules as classes, we made some assumptions in the generic parser code for other languages that don't quite align with ruby's notion of modules, but that'll be adjusted in the near future.
ScotterC|1 year ago
Both items above coalesce into a desire to 'rewind' back to the top of the process and try to get the context understood at the beginning, and have that clearly reflected to the user so that as you move through to details it gets easier to handle the nitty gritty without as much editing.
ScotterC|1 year ago