Show GraphQL, JSON, and JavaScript files in the navigator
The file navigator now lists .graphql, .gql, .json, .js, .mjs and .cjs files so you can browse and open them alongside your .http/.rest files.
Fixed
Body reference parser no longer confuses @-prefixed body text with file paths.
Previously, the inline body reference parser matched any < character anywhere in an @-prefixed line. This caused lines that were meant to be literal body text to be silently treated as file references.
# Before (bug) - parsed as file reference "./not-a-file-reference"
POST https://example.com/api
@{payload} < ./not-a-file-reference
# After (fixed) - correctly kept as inline body text
POST https://example.com/api
@{payload} < ./not-a-file-reference
The parser now validates that the @-prefix is a proper directive head (e.g. @body, @query, @grpc-metadata) before treating the line as a file reference. Template expressions like @{payload} and malformed heads like @1body are no longer misidentified.
@body inline now respected in GraphQL and gRPC bodies.
The from @body inline was only honored for HTTP bodies. GraphQL and gRPC builders ignored it, so < . file.graphql would still be loaded as a file reference even when you explicitly requested inline mode.
# Before (bug) - still loaded the file despite @body inline
# @body inline
# @graphql
POST https://example.com/graphql
< ./queries/workspace.graphql # loaded as file reference
# After (fixed) - treated as literal query text
# @body inline
# @graphql
POST https://example.com/graphql
< ./queries/workspace.graphql # kept as inline query text