-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Broken rendering output for IntegerLookup page #874
Comments
I've actually noticed this too for some docs symbols we are about to push out. It seems to happen always after the 10th You can actually see a trailing 0 after the second triple backtick that is messing up rendering. If you remove that from the source markdown, things are fine. |
Assigning myself to take a closer look. |
@MarkDaoust , @pcoet , How can we re-generate the doc from the original file, I see a different content and it is still not rendering new content in the website. keras-io/scripts/keras_core_api_master.py Lines 447 to 449 in 472f9b9
|
@sachinprasadhs I don't know how to regenerate an API doc, unfortunately. I checked in the autogen script (https://github.com/keras-team/keras-io/blob/master/scripts/autogen.py), but it looks like that only handles guides and examples. I'd guess the rendering issue is still outstanding, though. |
This issue is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. |
Thank you for fixing this, @mattdangerw! 👍 |
Problem statement
The bottom of this page: https://keras.io/api/layers/preprocessing_layers/categorical/integer_lookup/ looks incorrect (screenshot below) which seems to imply that the input source code may have incorrect syntax, but that seems to be correct (source, snippet included inline below).
Potential resolution
Perhaps that page needs to be re-generated and uploaded to the website to fix the rendering issue?
Screenshot of broken rendering on the page
Source documentation in code
The text was updated successfully, but these errors were encountered: