-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Mouser price import faulty? #540
Comments
… if it is marked as "new part" Related to #540
Austrian mouser returned some other formatted string, which caused problems on the old method. This fixes issue #540
The mouser api returns prices as locale dependent string depending on the selected country. Austrian mouser returned some string different to the expected one. This should be fixed with 1.11.1 Before, all parts which were marked as "New" by mouser were marked as "Announced". Now this only happens, if the part is new and no parts are instocked at mouser yet (otherwise its just active). |
@jbtronics thanks, that was fast. Tried it just now and it works, but accidently found another bug. And I have two questions, is import of part parameters supported? I just tried the same fuse holder and I don't get any parameters. |
Describe the bug
I just tried the import function from mouser and created an Search-API for it.
Now I tried to update a current part, but the prices of the mouser part are wrong.
It also says that the part was announced even though it clearly is released and in stock
To Reproduce
Try importing this part to partdb: https://www.mouser.at/ProductDetail/Littelfuse/65600201009
It says announced:
Prices all zero:
If the search already says anounced, shouldn't it not try to add prices?
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Server Side
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: