kaizenkodo/ChatMastermind
2
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Wiki Activity

Configurable glob and location on question and hist commands #18

Merged
ok merged 7 commits from cust_loc_glob into main 2023-10-20 09:47:05 +02:00
Conversation 0 Commits 7 Files Changed 9
+140 -101
ok commented 2023-10-19 16:18:47 +02:00
Owner
Copy Link
Copy Source

This pull request adds a new feature to the question and hist commands in the chatmastermind application. Previously, the default location for messages was set to 'db', which meant that messages in the 'cache' directory were not accessible. With this change, you can now specify the location of the messages using the new --location option.

Additionally, you can use the new --glob option to specify a glob pattern for message file names.

These changes allow you to easily select the location of messages and include messages from the cache directory in your commands.

This pull request adds a new feature to the `question` and `hist` commands in the chatmastermind application. Previously, the default location for messages was set to 'db', which meant that messages in the 'cache' directory were not accessible. With this change, you can now specify the location of the messages using the new `--location` option. Additionally, you can use the new `--glob` option to specify a glob pattern for message file names. These changes allow you to easily select the location of messages and include messages from the cache directory in your commands.
ok added 3 commits 2023-10-19 16:18:48 +02:00
Change type msg_location to an Enum instead of Literal to be able to get all values easy and improve type checks. 9b0951cb3f
Per default use only files with .msg suffix ignoring other files. 9a493b57da
Add --glob and --location flags to hist and question commands, to be able to specify the location and files they should use. 114282dfd8
juk0de added 1 commit 2023-10-20 08:25:15 +02:00
chat: changed default glob to '*.msg' in all ChatDB functions 480987774d
juk0de added 1 commit 2023-10-20 08:52:52 +02:00
README: added new 'question' command parameters f2852c1448
juk0de force-pushed cust_loc_glob from f2852c1448 to d2a3ab0adb 2023-10-20 08:57:34 +02:00 Compare
juk0de force-pushed cust_loc_glob from d2a3ab0adb to e74d5417ad 2023-10-20 09:01:07 +02:00 Compare
juk0de force-pushed cust_loc_glob from e74d5417ad to 9c7483ec51 2023-10-20 09:03:35 +02:00 Compare
juk0de added 1 commit 2023-10-20 09:15:03 +02:00
cmm: limited the message locations for the new cmm parameters to those that make sense 049edbf940
juk0de force-pushed cust_loc_glob from 049edbf940 to 5774278fb7 2023-10-20 09:16:11 +02:00 Compare
ok merged commit 17c6fa2453 into main 2023-10-20 09:47:05 +02:00
ok deleted branch cust_loc_glob 2023-10-20 09:47:05 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
juk0de ok
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kaizenkodo/ChatMastermind#18
Delete Branch "cust_loc_glob"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?