.j2 file in code_dir causing rendering error about hexo

[stevenjoezhang]

The current situation is more complicated than I thought. Hexo's current database models Page and Asset are not well-suited for expressing "code" files (including not only j2 but also js or css files):

1. Assets are not rendered, but their content is also not stored in the database (usually used for handling multimedia resources like images, but not plain text files);
2. Pages are always rendered, even if they are non-markdown files such as the aforementioned j2, js, or css. Typically, users do not want these files to be rendered as pages or converted to other formats (though there are exceptions, such as plugins used for compressing js files).

I have not found a very elegant solution about how to handle files in code_dir.

[D-Sketon]

j2 becomes html and loses the content field? (Is this normal behaviour?)

And #5121's modification resulted in an undefined exception:

hexo/lib/plugins/tag/include_code.ts

Lines 57 to 58 in 093dc2d

	let code = doc.content;
	const lines = code.split('\n');

[stevenjoezhang]

I think setting code_dir to skip render should solve the problem. This should be feasible during the loading process in Hexo.

[uiolee]

This may be related to version. v7.1.1 does not have this problem

[uiolee]

#5121's modification resulted in an undefined exception:

hexo/lib/plugins/tag/include_code.ts

Lines 57 to 58 in 093dc2d

	let code = doc.content;
	const lines = code.split('\n');

I guess that's a problem but not a critical one. code_dir itself should not be rendered