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

Jump to bottom

Conceptual for should be treated as case insensitive #2792

Closed
marcoscaceres opened this issue Mar 18, 2020 · 1 comment · Fixed by sidvishnoi/respec-xref-route#58
Closed

Conceptual for should be treated as case insensitive #2792

marcoscaceres opened this issue Mar 18, 2020 · 1 comment · Fixed by sidvishnoi/respec-xref-route#58

Comments

@marcoscaceres
Copy link
Member

For example:

[=list/For each=]

And
[=List/For each=]

should both link.

Right now, [=List/For each=] is not found.
@sidvishnoi
Copy link
Member

Found a case where we can't simply just lowercase the forContext: [= AbortSignal/add =] - add is a concept here, not a method.
But on xref server, we can try the lowercase forContext if the original one is not found.

@sidvishnoi sidvishnoi mentioned this issue Mar 18, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(search): fallback to lowercase forContext for concept types sidvishnoi/respec-xref-route
2 participants
@marcoscaceres @sidvishnoi