-
Notifications
You must be signed in to change notification settings - Fork 54
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
Templates Lack Syntax Highlighting and Structure Uneditable #76
Comments
Hi Matt, Thanks for trying our templates feature! To enable syntax highlighting, you can click on the "No template" option from the Template drop down menu.
Is this helpful? All the best, |
@mluckcuck was my previous answer helpful? |
Sorry for the slow reply @anmavrid , now that I'm back to using FRET (and doing things with the templates) I remembered this issue. I can see that selecting 'No Template' works, but it would never have thought to try that. It seems counter-intuitive to select a template, begin filling in the template, and then un-select the template. Also, give that if I have typed FRETISH text and then select a template, it overwrites it, I would have thought the un-selecting the template would have also deleted what I'd typed. Besides that, it's ~ 3 more clicks. I suppose I expected it to highlight the fields as each field is completed, or after saving the requirement or something. |
Also (I've just found this) if I:
It deletes the FRETISH text I'd written. |
We've just started looking at the templates, which seem quite useful and are (helpfully) extendible too.
But if I use a template to build a requirement, it has no syntax highlighting, which makes it hard for me to parse the requirement.
Also, after saving the requirement and coming back to it, it is still 'a template' so it is uneditable (e.g. I cannot change the if..then.. structure of Change State's response). I'm in two minds about if they should be editable, after saving (i.e. once saved it becomes a normal requirement) but I sort of expected it to become a 'normal' text requirement after it was saved.
The text was updated successfully, but these errors were encountered: