Problem with transitive request references not being resolved
See original GitHub issueHi @AnWeber, first of all, thanks for httpyac. I really appreciate your work.
I noticed a problem with nested request references where each request resides in a dedicated .http file.
Starting point
File: a.http
# @name getHttpbinA
GET https://httpbin.org/get?source=getHttpbinA HTTP/1.1
X-Foo: barA
File: b.http
# @import ./a.http
###
# @name getHttpbinB
# @ref getHttpbinA
GET https://httpbin.org/get?source=getHttpbinB HTTP/1.1
X-Foo: barB-{{getHttpbinA.headers["X-Foo"]}}
File: c.http
# @import ./b.http
###
# @name getHttpbinC
# @ref getHttpbinB
GET https://httpbin.org/get?source=getHttpbinC HTTP/1.1
X-Foo: barC-{{getHttpbinB.headers["X-Foo"]}}
Observation 1:
Calling getHttpbinC
in vscode yields ReferenceError - getHttpbinA is not defined
The direct dependency getHttpbinB
was resolved correctly; whereas getHttpbinA
was not.
The httpyac variable view shows
Observation 2:
Calling getHttpbinB
in vscode works as expected.
The httpyac variable view shows
Calling getHttpbinC
then without clearing the response history works.
However, the httpyac variable view misses getHttpbinA
Observation 3:
If all 3 requests reside in a single .http file calling getHttpbinC
works.
Also, the httpyac variable view is complete
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Reference transitive not working when app and libs ... - GitHub
The issue is there is a .NET Framework app which references a .NET Standard Library, which references a library multi-targeted to .NET Standard ......
Read more >Disable transitive project reference in .NET Standard 2
The problem is that I can use Model in the Web project (i.e. the compiler sees the type Model and I can do...
Read more >Dependencies of project reference not copied to output ...
This usually fixes the issue as PackageReference restore style will copy the transitive dependencies accordingly and will choose the right one ...
Read more >Solving Transitive Dependency Issues in .NET Core
Transitive dependency issues can be hard to identify and solve. Here's my unscientific approach to fixing them.
Read more >Understanding dependency resolution - Gradle User Manual
Dependency resolution will fail if the required artifacts are not available in any repository specified by the build, even if the local cache...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@AnWeber Great. I have tested both fixes with v5.0.4 successfully. Thank you.
I love how detailed you describe your Issues.
Will check it out.Unfortunately, this is another mistake.