-
Notifications
You must be signed in to change notification settings - Fork 223
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
code editorial screen shots are not visible #4
Comments
Hey, nothing has been changed recently. The editorial code isn't available for all problems, just some of them. I can still view the code here as usual: https://github.com/akhilkammila/leetcode-screenshotter/tree/main/editorial_code If you are experiencing something different, could you lmk in more detail |
Oh ok, I see. Yeah it is supposed to show the whole editorial. I am not having the same issue. It should look like this (and as you scroll down, the rest of the article is there): Could you lmk if the download button works? Does it work on a different browser? To me, it seems to be an issue with github displaying the png file. This might help: https://github.com/orgs/community/discussions/56585. I think trying a different browser or clearing cache could be a good place to start. Actually, if you are from India, this part of the thread is probably the fix: https://github.com/orgs/community/discussions/56585#discussioncomment-7150482. |
My issue was same as the https://github.com/orgs/community/discussions/56585#discussioncomment-7150482. I have switched the network and its working now. Thanks a lot. You have made a really helpful repository. I was thinking if one could make a pdf book of the screenshots and the questions. It would be like a DSA problems exercise book lol. You have really interesting projects. Could you please help me and guide me on how to build such bots .I would like to connect and work together on something. |
The code editorials are not visible for any questions. Im not sure if they have been taken down. Any updates
The text was updated successfully, but these errors were encountered: