-
Notifications
You must be signed in to change notification settings - Fork 95
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
Improve handling of aliased functions #14
Comments
The 404 page I think would have to be set up through the webserver, but if you want to take a stab at it you could assume the page's name to be whatever you please, and then I can change the webserver settings to match that. |
baldurk
added a commit
to baldurk/docs.gl
that referenced
this issue
Nov 8, 2014
baldurk
added a commit
to baldurk/docs.gl
that referenced
this issue
Nov 8, 2014
baldurk
added a commit
to baldurk/docs.gl
that referenced
this issue
Nov 8, 2014
baldurk
added a commit
to baldurk/docs.gl
that referenced
this issue
Nov 8, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From discussion on #13 -
For aliased functions (like glUniform3f -> glUniform or glEnablei -> glEnable) it would be useful to have search results match when they are entered, and return the target of the alias function in the search results instead of nothing.
On top of that, if there is a 404 page for when an invalid page is specified (e.g. http://docs.gl/gl4/glNotFound) this page should check to see if the page is an alias source, and if so redirect to the alias target.
The text was updated successfully, but these errors were encountered: