Replies: 2 comments 1 reply
-
|
There was a big change when moving from the simple validate_snippet.py to using a true Linter called FMLint. Prompt the agent to disclose where the instructions may be happening. It needs to determine if that is coming from deterministic output or the models probabilistic output. You can ask it if it is referencing the linter for verification before final output. I've been testing other areas and haven't been using it for as much code generation lately. "Please outline the steps you take just prior to delivering the final code output for me." |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I just pushed a change which updates FMLint to try to address agentic code generation. We may still have some edge cases as operators can appear within XML, within the CDATA of the XML of an Insert Text step and within calc code itself. Addressing these across the variety of outputs may take a bit more testing. I need to create a test suite of all the various cases. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have noticed that the agent generates calculations with the
>and<symbols, which cannot be used within a FileMaker calculation.For
>the agent must use>and for<the symbol<must be used. Additionally for≥must be used>=and for≤the symbols<=must be used.I am not quite sure where this information should be placed most appropriately within the entire system.
Beta Was this translation helpful? Give feedback.
All reactions