8000 Swift: incorrect access level information · Issue #52 · upstash/context7 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Swift: incorrect access level information #52

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

Open
uros-mil opened this issue Apr 21, 2025 · 1 comment
Open

Swift: incorrect access level information #52

uros-mil opened this issue Apr 21, 2025 · 1 comment

Comments

@uros-mil
Copy link

I tried using context7 in Claude Desktop to ask: “Is there a package access level in the Swift language?”
Claude correctly used resolve-library-id (and found /swiftlang/swift) and get-library-docs to query the data (topic: access control), but the response from context7 was lacking info about package access level.

After that, I refreshed the Swift library, but the result remained the same.

Finally, I asked Claude to use tavily to verify the answer. It then found that the package access level does exist and corrected the previous response.

How is it possible that specific access level was missing, when Access Control page of Swift documentation clearly states this level?

@enesakar
Copy link
Contributor
enesakar commented Apr 22, 2025

The first version of our parser focused on enriching and searching code snippets so we are aware it misses some information if there is no code section relevant. We can easily add informational content in addition to code blocks, but I am a little worried that when we add text blocks then the efficiency of the code based system might decrease. Another idea might be providing two separate functionality:
1- coding syntax and api questions
2- informational documentation questions.

The current system is built for 1, with assumption that 2 is already done by web search by LLMs.

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
0