-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] : Bug in Custom prompt initalization mechanism #381
Comments
Indeed, however the /find should only be shown when RAG is activated. |
I'm currently looking into the issue i'll keep you in touch as soon as possible |
Hello @stephanj some feedbacks on this topic it seems that the behavior i did observe was coming from my "deprecated" DevoxxGenieSettingsPlugin.xml file. Default prompt initlization from last version of code (with find command) was dumped by the xml state loaded from the persisted xml file. I do not have solution at this point as i consider that this file can represent modification done by the user so i assume the user want to reload systematically his custom prompts even after an update of the plugin in IDEA. However i'm working on a branch where with the following features :
|
Sounds like a plan, thanks for the update. |
It seems that the method :
is called twice at the initlization of the ToolWindowcontent the first time with the Constructor
public DevoxxGenieStateService()
the second time by the loadstate method
public void loadState(@NotNull DevoxxGenieStateService state).
The second pass the customPrompt list is coming with only 4 values (dont know why at this point)
The bug can be observed directly in the welcome message where command prompt are dynamically added
and we cannot see the newly added FIND command method.
@stephanj do you confirm?
The text was updated successfully, but these errors were encountered: