-
Notifications
You must be signed in to change notification settings - Fork 5
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
"#123 by Submitter was closed 0 years ago" (Caused by System Settings > User Agent unchecked) #9
Comments
Looks like when I cleaned up the branch for a final release, I didn't make sure I filtered out whitespace. So delete extra whitespace / newlines in the repo list text area. I'll patch in it the next version. |
What happens if you edit From: Logger {
id: logger
name: 'githubissues'
// showDebug: true
} To: Logger {
id: logger
name: 'githubissues'
showDebug: true
} Then run: QT_LOGGING_RULES="qml.debug=true" plasmawindowed com.github.zren.githubissues It will normally show:
but I assume |
Ok Zren, done and solved.
I remembered something related to the User Agent in the Plasma Settings: in fact I had the "Send Identification" disabled, that's why the problem on the User Agent. Now everything works and all my repos are correctly fetched, sorry if I wasted your time with these silly things. Finally, thank you again for your work: I love your plasmoids and I'd like to add them to my Look-And-Feel themes as dependencies, obviously while giving you all the credit you deserve. Let me know if you don't want to or you have special requests to make! Have a nice Sunday! |
Todo: Parse
|
HI Zren, thank you for this widget.
I installed it from the KDE store and tried immediately to add my repos like in the following picture.
Sadly, the widget is showing only this (I guess) "placeholder" string as in the following image:
I tired many times refreshing the widget and adding other repositories with more issues (wrt my repos) (both closed and open) but nothing seems to change.
Could this be a problem related to Github APIs, maybe?
Thank you for your attention.
The text was updated successfully, but these errors were encountered: