-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
Reference to local file doesn't work #65
Comments
I am not sure its mandatory to have this structure. But this is how i make it work. the reference should point to the type of object you want and inside the file myObject.yml
|
@fsimard thanks for the hint, but that doesn't work for me. I always get After upgrading to 0.7.9 i get a slightly more expressive error message: |
Mmm interesting. @xino12 can you have a look at this? Do you have an idea of why this is happening? |
I upgrade to the last version and use 2.0.0-rc1 version using reference and I have the same problem |
me, too :). I'm trying to include a yaml file by reference and fails with that message, where the offending character is the first character of the included file. So, character 'a' is referring to the 'a' in 'asyncapi:' on the first line. |
This bug is gonna get solved as soon as we release our new JS parser in the next weeks. |
The generator is now using the new parser, which takes care of this. Closing. |
I am playing around with references to local files and can't get it to work with the generator and referencing a yaml file.
basic_example_refs.yml:
myObject.yml:
Both are in the same directory. I am trying this on Windows. When doing this with the myObject.yml file, I get the following error:
After reading reusing messages, I thought that yaml files can be used. The 2.0.0-rc1 spec and this issue indicate that it might not be possible, though. However, when I am trying the same thing with a local json file, it works:
Changed basic_example_refs.yml:
myObject.json:
Is this an issue of the generator or am I doing something wrong here? Thanks in advance,
Marco
The text was updated successfully, but these errors were encountered: