-
Notifications
You must be signed in to change notification settings - Fork 20
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
example of using resulting ast #6
Comments
also, yes, i did make guesses as to where the errors might be using all of the given numbers and checking with the line numbers in sublime. no indication in code related to messages and in the apiary.io interface, warnings do not show up at all. |
@phamdt those numbers are as follows :: you can easily see number of selected characters in SublimeText. However I suggest to use SublimeLinter to see it right in the editing window. |
thanks! i'm guessing you meant :selectedCharCount:somethingElseIStillDoNotGet. the selected chars was enough to find it. also, i did end up installing SublimeLinter and its related packages. for some reason the above two errors disappeared after doing so. regardless, i still think a brief explanation/example in the read me would be helpful. |
:) It is quite simple, albeit it does not look like. Let me illustrate: Where In Snow Crash an error / warning report can span across multiple non-continous blocks of blueprint source text. That is why this string can be something "crazy" like Hope it is a lot clearer now. If you find a good formulation for this that can be put into the README file I will be happy to merge such a PR. |
i've just installed the plugin and it's not clear to me as to how to use the ast file resulting from the parse command. specifically, i see the following warnings:
while the error text is simple enough to understand, it's not clear where i'm looking for each one. it would be helpful then to provide some explanation of the warnings/errors and provide an example error/explanation in the read me.
The text was updated successfully, but these errors were encountered: