feat: prevQuery.json -> globalScope.json, painted the tui elements#105
Merged
feat: prevQuery.json -> globalScope.json, painted the tui elements#105
prevQuery.json -> globalScope.json, painted the tui elements#105Conversation
This is just convenience to quickly inspect the ongoing conversation by listing it. Will simplify inspecting and resuming chat which is currently worked on
We now have a theme.json and default colours. Also a NO_COLOUR arg which removes any ansi colours
Setup still isn't colourized, but that's the last one
4f0172a to
59af9ab
Compare
prevQuery.json -> globalScope.jsonprevQuery.json -> globalScope.json, painted the tui elements
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another breaking change in strides towards becoming the most integrated CLI tool in the world! Althought the update is backwards
compatible, so no need for any updates
Naming it
prevQuery.jsondidn't really fit anymore,global scopematches the terminology withdir scopebetter. This alsoopens up the avenue for chats which are bound in other ways.
git scope, perhaps? Who knows where we're heading with this.In addition, on
clai chat continue <empty-string>, the dirscope conversation is continued, followed by global scope.The "continue" here is practically listing all the messages in the conversation in a convenient way, so that it's possible
to see how the LLM is doing.
Additional features: