[BUG] Code blocks are not properly rendered in the README.md file

[zolakt]

I'm not sure if I'm doing it right, but I just can't get it to work. I'm using the same example as you have on your demo app README.md.

This is the code I add to the readme file:

function hello() {
    console.log('hello world !');
}

And this is the output I get:

As you can see it's not transformed to html correctly. There is no pre block. There is no "language" attribute on the code block... so prism.js doesn't pick it up.

I'm using the the 1.1.9 version. Tried also with 1.1.8 and 1.1.7... same result.
Am I doing something wrong or is it a bug?

Unrelated, but table syntax also doesn't work in README.md

[jayanezj]

Hi, you have to use the GitHub Flavored Markdown . There is a problem in version 1.1.9 (check this), but if you use the development branch it will work correctly.

[zolakt]

Ok thanks. Although, I tried with 1.1.8 and 1.1.7... got the same error.
I'll have to wait for a release, can't use the development branch, since it could break the CD at some point.
For now I resorted to writing html tags.

[jayanezj]

Ok thanks. Although, I tried with 1.1.8 and 1.1.7... got the same error.
I'll have to wait for a release, can't use the development branch, since it could break the CD at some point.
For now I resorted to writing html tags.

If you are concerned about version stability then switch to version 1.1.8 and write the code block as follows in the README.md:

```javascript
function hello() { 
    console.log('hello world !'); 
} 
```

The result will be:

function hello() { 
    console.log('hello world !'); 
} 

[zolakt]

Thanks. I'll give it a try again, although I did get the same problem with 1.1.8.
Also I don't think 1.1.8 annotates static members, and that is a much bigger showstopper than formatting code blocks.

[admosity]

This is how https://github.com/compodoc/compodoc-demo-todomvc-angular looks like with version 1.1.9.

This also looks to be the same issue: #776

Downgrading to 1.1.8 fixes this particular issue.

[lock]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.