Skip to content

Commit b614279

Browse files
committed
CEDARScriptEditorException: improved prompting in error message
1 parent b5eb901 commit b614279

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

src/cedarscript_editor/cedarscript_editor.py

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -54,12 +54,11 @@ def __init__(self, command_ordinal: int, description: str):
5454
f"\n<error-location>COMMAND #{command_ordinal}</error-location>"
5555
f"\n<description>{description}</description>"
5656
f"\n{note}"
57-
"\n<suggestion>NEVER apologize; just relax, take a deep breath, think step-by-step and write "
58-
"an in-depth analysis of what went wrong (specifying which command ordinal failed), "
59-
"then acknowledge which commands were already applied and concisely describe "
60-
"the state at which the file was left (saying what needs to be done now), "
61-
f"then write new commands that will fix the problem{previous_cmd_notes} "
62-
"(you'll get a one-million dollar tip if you get it right!) "
57+
"\n<suggestion>Reflect about common mistakes when using CEDARScript. Now relax, take a deep breath, "
58+
"think step-by-step and write an in-depth analysis of what went wrong (specifying which command ordinal "
59+
"failed), then acknowledge which commands were already applied and concisely describe the state at which "
60+
"the file was left (saying what needs to be done now), then write new commands that will fix the problem"
61+
f"{previous_cmd_notes} (you'll get a one-million dollar tip if you get it right!) "
6362
"Use descriptive comment before each command; If showing CEDARScript commands to the user, "
6463
"*DON'T* enclose them in ```CEDARSCript and ``` otherwise they will be executed!"
6564
"</suggestion>\n</error-details>"

0 commit comments

Comments
 (0)