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

add spector test for jsonl #6201

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

add spector test for jsonl #6201

wants to merge 2 commits into from

Conversation

tadelesh
Copy link
Member

No description provided.

@microsoft-github-policy-service microsoft-github-policy-service bot added the lib:http-specs For issues/prs related to the @typespec/http-specs package label Feb 28, 2025
@tadelesh
Copy link
Member Author

when regen doc for spector, i encountered this error. @timotheeguerin is it a problem in spector or in http lib?
image

@azure-sdk
Copy link
Collaborator

azure-sdk commented Feb 28, 2025

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • @typespec/http-specs
Show changes

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension


@doc("Test of jsonl stream.")
@scenarioService("/stream/jsonl")
namespace Stream.Jsonl;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when regen doc for spector, i encountered this error. @timotheeguerin is it a problem in spector or in http lib?
image

replying here so we can have a thread. I think this is the same problem the Azure specs have where the namespace conflict with an existing namespace from a library and we add to add _Specs_ prefix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lib:http-specs For issues/prs related to the @typespec/http-specs package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants