You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on this as a standalone project which is designed to bring header block comment generation to Interleave. At the moment, the code is still a work in progress, but some functionality is already there. Before I go too far though, I'd love to have some feedback on what people think should be in a source file headerblock.
// ┌──────────────────────────────────────────────────────────────────────────────────────┐ \\// │ Eve 0.3.5 - JavaScript Events Library │ \\// ├──────────────────────────────────────────────────────────────────────────────────────┤ \\// │ Copyright (c) 2008-2012 Dmitry Baranovskiy (http://dmitry.baranovskiy.com/) │ \\// │ Licensed under the MIT (http://www.opensource.org/licenses/mit-license.php) license. │ \\// └──────────────────────────────────────────────────────────────────────────────────────┘ \\
and there are plenty of others.
My general thoughts are that the headerblock should not only be easy on the eye for a human, but also something that is potentially machine readable. So potentially incorporating a YAML section for metadata is one thing I've been considering.
Here are some early examples of the kind of thing I'm thinking about:
Hey All,
Working on this as a standalone project which is designed to bring header block comment generation to Interleave. At the moment, the code is still a work in progress, but some functionality is already there. Before I go too far though, I'd love to have some feedback on what people think should be in a source file headerblock.
Here are some examples from around the web:
jquery
eve
and there are plenty of others.
My general thoughts are that the headerblock should not only be easy on the eye for a human, but also something that is potentially machine readable. So potentially incorporating a YAML section for metadata is one thing I've been considering.
Here are some early examples of the kind of thing I'm thinking about:
The leading comment line incorporating a tilda (
~
) would be used to indicate that the comment block is potentially machine parseable.Thoughts?
The text was updated successfully, but these errors were encountered: