Skip to content
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

Open
phamdt opened this issue Feb 20, 2014 · 4 comments
Open

example of using resulting ast #6

phamdt opened this issue Feb 20, 2014 · 4 comments

Comments

@phamdt
Copy link

phamdt commented Feb 20, 2014

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:

warning: (3)  unable to parse additional parameter traits, expected '([required | optional], [<type>], [`<example value>`])', e.g. '(optional, string, `Hello World`)' :21574:234
warning: (6)  empty response message-body :25880:13

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.

@phamdt
Copy link
Author

phamdt commented Feb 20, 2014

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.

@zdne
Copy link
Contributor

zdne commented Feb 20, 2014

@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.

@phamdt
Copy link
Author

phamdt commented Feb 20, 2014

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.

@zdne
Copy link
Contributor

zdne commented Feb 21, 2014

:)

It is quite simple, albeit it does not look like. Let me illustrate:

subl1

subl2


Where :52:11 means starting at character with index 52 and spanning across next 11 characters (see the first screenshot).

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 :103:11;118:8;130:14;148:18 (:index:size;index:size ..).

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants