-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Bug]: User name not matching #6
Comments
After a bit of digging I may have found the issue. |
A similar bug occurs in |
Thank you for opening the issue! The error occurs because apparently FA admins do not have a status character in front of their username (~, !, ∞, etc.). Unfortunately, the status character is contained in the same tag as the username (why they didn't use a child |
Release 3.9.3 is available :) |
Aaaaand I forgot about the watchlists x3 |
🤣 Well, I have been working on a little fix in my project as well. My idea revolves around getting the user name from the URL. So I am getting the URL from the And I have noticed that for the watchlists there is alway a separating space between the status and the username. |
But anyways. If I find more issues or other bugs... |
I like the property:url solution! You should submit a PR so we can integrate it with FAAPI :) As for watchlists: my solution detects the admin logo, but you’re right, there is a space and it would work much better by simply parsing the link URL and then looking for the status separately. |
Oh! As I have mentioned they have "-" as status-
if As I have mentioned simply removing any leading "-" would be problemantc since some usernames have "-" amd "--" included at the beginning. |
I will try to make a PR and try to make the code look nice 😅 |
I have checked "marioea" but there is no issue with them. The User object correctly parses their name as "marioea" and "-" as status. api = faapi.FAAPI(cookies)
u = api.user("marioea")
print((u.name, u.status)) # ('marioea', '-') |
Hmm then I must have overlooked something there 🤔 |
Version
3.9.2
What happened?
I have encountered a strange bug.
A username is not properly returned by the api.
For the username "ashwolves5" a user object can be created with.
However, the returned user name from the user object is not matching.
user.name
returns only "shwolves5", which obviously causes and error when this name string is uses to creae another user object with the api.How to reproduce the bug?
(As described)
Relevant log output
No response
The text was updated successfully, but these errors were encountered: