Another idea-
How about upon "new snippet" the snippet code box is pre-populated with whatever best practices determines is a good header for the snippet. Something like:
// ***********************************
// Snippet:
// ***********************************
// Version:
// Date:
// Author:
//
// Description
//
// CONFIGURATION
// END CONFIGURATION
The developer wouldn’t be committed to it of course, but it would eliminate having to go back and look at another snippet to see how it was done for those who like to be consistent. I know I’d appreciate it.
The above example is the way I’ve done mine. But I’m NOT suggesting it is the best way. I use it as a familiar example only. Powers that be would be better to determine a recommended standard.
Just a thought. Of course, mostly I develop snippets outside that text box anyway... but I could copy that bit out of the box into my code editor...
MODX Staff
☆ A M B ☆
