-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General improvements to our hacky implementation of IMP-Doc #802
Comments
The first line should only be the resource location of this function, according to the IMP-Doc. |
There are some examples on the wiki that show it is possible to start with a capital. |
Those examples are not for describing functions 👀 |
tbh, I think it'd be cleaner to have syntax like this
For IML doc not describing functions ¯\_(ツ)_/¯ |
I will keep this open to track general improvements to our IMP-Doc implementation 👀 |
Sounds like the issue here in general is that people may not necessarily want to comply with the IMP-Doc header format when using the block comment style at the beginning of their function. Maybe the solution is to check for a resource location and, if one exists, verify that it matches the current function location. Otherwise, if it fails to parse a resource location at all, just assume it's a regular comment header. (?) Edit: or some kind of "strict IMP-Doc" toggle in settings (that's disabled by default)? Edit 2: or... another comment prefix (like |
Try writing #> in the first of mcfunction file, then put some comment with capital letter
![image](https://user-images.githubusercontent.com/57800056/101901687-0658d780-3be4-11eb-9743-e243a2a3fb27.png)
Then it will show up error
The text was updated successfully, but these errors were encountered: