Closed KittyGiraudel closed 10 years ago
Compromise: Lets ignore them in SassDoc.
I am okay with cleaning up data on SassDoc's side rather than ScssCommentParser's side. What I don't want is moving all this —basically useless— stuff to the view.
Okay. Fixed the issue with returning context : undefined
in sasscommentparser@0.0.19
. Will create a PR to ignore context : 'unknown'
We should update view to clean my now useless safeguards:
I assigned @HugoGiraudel to update the view.
Currently, only comments beginning with
/**
and ending with*/
are parsed. That means a comment beginning with/*
won't be treated as documentation.I think everybody is perfectly fine with this right now. That's how most documentation systems work, including the popular JavaDoc.
Now, running our test, here is what data looks like.
This is a mess, and it is partially my fault. I use
/** */
everywhere. Every time I want to write a comment about something, I go/** */
for instance:This is perfectly fine, right? I should be able to use the type of comment I want wherever I want, especially since it doesn't anything to do with SassDoc in this example.
Now, we still get a lot of things documented because of this, that are then stripped (basically not displayed) once in the view.
My point is: a documented item without any annotation registered should simply be removed before heading to the view. An item with no annotation is obviously not a documentation. We should not have to move this crap around.
Any thought?