Bugs and issues

Issues and feature requests

These are some issues I've already raised on github with dev team

1. Markdown extension docs should include instructions to "include" the components
2. Better error message when markdown extension is mispelled
3. Use "snippets" pattern to import test code into docs
4. Support inline components in markdown
5. Glow to please support line numbers when using fence blocks
6. Adding [codetabs] to any markdown page gives runtime chrome error Failed to resolve module
7. Access to current Nuejs version as a system variable

Things that need discussion or polish (my 2 cents)

The following things I didn't quite feel the love;

Libraries, Include, Exclude

1. Including and Excluding assets felt like a very manual way to optimise payload. It feels like it should simply not exist ? i.e. couldnt Nue just employ some kind of smart tree shaking to determine what things are needed and what are not and deliver an optimal payload automatically?
2. Does this mean that javascript code won't behave as expected?
3. How do I import just one function from a library?
4. If two different pages both import just a function from a lib, how do you write singletons (static) instances?

3. Stability?

1. I know I said in my "fabulous features" that because so much has been removed it feels really rock solid. That's kind of true, but there are moments where things just suddenly don't behave and I can't report it as a bug because the dev team say they can't reproduce, and it feels like I'm gaslighting myself.
2. For the issue above, it turns out I actually had remembered [! /img/myimage.jpg] totally correctly, but for some unknow reason, Nue just REFUSED to render the image, instead it rendered the actual markdown. The only way I managed to get it working was to cut and paste [! img/favicon.jpg] from a different project, and suddenly it started working again, as if one of the characters I had typed had some encoding issue, or the generated code by the nue compile step has an encoding problem. This is not the first time this type of "HUH???" moment ...has happened. I even stopped and started nue, and deleted the .dist folder just in case. I will have to watch this space carefully.
3. I normally wouldnt make such a big deal of this; but, when trying to learn a new system, if you hit one of these bugs during your learning, it can be a dealbreaker that is so confusing that you just give up and move on and use something that actually works for you. So, I will be watching very carefully to see if this happens again soon enough for me to say this is actually a real concern. The next time this happens, I'm going to deploy the page, and see if the bug is local to my machine, or persists to production.

Update: it happened again, and literally in this very page. (Which is why there's a bit of gobblygook in the text a bit further up just to surround the two instances of the image tags)

This is quite important; because I believe these types of issues go unreported. A new user doesnt even know that something is an issue, they just think they've misunderstood it, and decide, "this is too complicated for me", or, "it's not as simple as the authors claim it is" and they dont report it as a bug.

update: 11pm Thur 12th

1. I reported the bug on github issues; and it was picked up by 1 of the devs, we had an exchange on github issues and we identified the root cause and found a simple workaround within 2 hours.