Output CSS format in docs is not clear about stylable HOT 4 CLOSED

@idoros is there any disadvantage to manual name-spacing? (performance, etc)

i can't think of a reason not to use @namespace, and this means we should show it in every example we make in order to imply it's a best-practice. (we will also add it to the best-practices guide)

from stylable.

namespace has no performance, target size, and I'm not sure it's best practice, but it will give clarity to the output CSS if we when we show it.

The issue is less about the namespace, and more about writing the output CSS with the actual scoping results.

from stylable.

I started implementing this, and abandoned my changes mid-work. I've reversed my train of thought on this. Adding name-spacing in examples may be less accurate, but it makes them readable without adding unnecessary complexity.

I suggest we go through them one-by-one and decide how we handle them.

For example, when I tried to add namespacing to the example in the pseudo-classes reference guide, the already complex example got too hard to read. And on the other hand, I felt the namespacing didn't add any new information that was relevant to this reference.

Let's go over them 1-by-1 and decide for each one where it makes sense.

from stylable.

@brucelawson can you look at the new examples format in our docs? i'm closing this issue, and if you think it's still not good enough we'll reopen.

from stylable.