• Content count

  • Joined

  • Last visited

About dkurok

  • Rank
    Level 2 Stud

Recent Profile Visitors

144 profile views
  1. v3

    Hello Nathan, I've send you a forum-message with my swagger-file. regards Dietmar
  2. When clicking on a part in the "My Lost Parts" overview, the window with the "Part Summary" is opened. In this situation it would be nice if it has the "My Lost Parts" tab activated per default (and not the "Add this part to list/inventory" tab. I want to see in which set(s) the part is missing on the first view. Best regards Dietmar
  3. Great! I just tested it and now I think I understand what it returns. Am I right with the following? : A tupple (LEGO-design-id , LEGO-Color-ID) is mapped equivalent (in the meaning of bidirectional) to a (LEGO-Element-ID)
  4. I also feel that such kind of "customization" gets too complicated - not only to implement in the engine, but also too complicated for most of the users
  5. v3

    OK, I do understand the limitations of the framework and can live with the "missing" ordering (in my use of the API in most scenarios I will fetch all data by taversing through the "next" as long as it is not null). Are you using "Django REST Swagger" for generating the sager docu from your API? Meanwhile I added a lot of information to a copy of your original swagger-YAML trying to bring in also information and modelling of the paramters and especially schema of the result (which afterwards makes generating a C#-based client just a few clicks and importsinto a project). Due to time limits (this is really a hobby for me) I have it not for all functions (I started with those I know I (will) use). If you like, I can give you a copy of that file for a first review. Maybe it is easier to use a YAML-file for the documentation which you can update manually (and not by the automatic generation based on your API-implementation)... Best regards Dietmar
  6. I tried allparts-function and it returns both of my 70496. In the result I cannot distinguish/find out from where they are coming (from part-list or from setsminus parts of lost-parts) - but the result -as far as this little test can proof- is fine and together with the /parts-function it fits my needs. Thank you!
  7. Nathan, can you please explain what the function returns? I still get for example: api/v3/lego/elements/6031144/ { "part_id": 11548, "color_id": 70, "element_id": "6031144", "design_id": "88585" } and then with the returned part_id /api/v3/lego/parts/11548/ I receive { "detail": "Not found." } (404) (I used API V3 testpage on for making sure I have no errors in my implementation) So what kind of part_id does lego/elements/{id} return? Best regards Dietmar
  8. I think it would be best if the spare parts of an export a marked as such. So whereever the export is used afterwards, the spare parts can be clearly distinguished from the regular parts. So it depends on the definition of the export-format (not on Rebrickable) to sort these things out. The Rebrickable-API V3 (and also V2) for example clearly marks a part of a set as spare part. Other export-formats may not have this marker. IMHO Rebrickable behaves correct in such cases when it exports also the spare parts (they belong to the inventory of the set as delivered). But to your wish: for some of us it really make sense to have the option to not export the spare parts; so make it an option/checkbox would be "nice to have".
  9. I'm fully with you! Rebrickable should save nearly all my last sortings, filterings,... on a per page base (so different criteria for Partlists, for Setlists, for MOCs,...) Would be nice if we could get that....
  10. Me too! Would be nbice to have it! @TobyMac: Put it in the suggestions-area; than we can vote for it...
  11. Hello, can someone please explain what exactly the API-function GET /api/v3/lego/elements/{id}/ is used for? In detail: - What ID is the parameter in (Lego-Element-ID, LEGO-design-ID,....)? - What is the result? The part_id seems not to be a Renrickable Part-Number Try for example 18862 for the {id} . It returns: { "part_id": 11548, "color_id": 70, "element_id": "6031144", "design_id": "88585" } So this seems to be LEG-Element-IDs and Design-ID for the queried ID. But the part_id is not a valid Rebrickable-ID/part_num... To be honest, I'm not so familar with the way especially LEGO is numbering their parts;so maybe someone can explain here or guide me to some ressource to understand... Best regards Dietmar
  12. Wasn't aware of this behaviour up to now... I just tested /api/v3/users/{user_token}/parts/ with the somehow rare "70496" (I know I've got texactly two of them; one in a set (8285-1) and one in my loose parts). It returns only the one from my loose parts. From the description of the function it should " Get a list of all the Parts in the user's LEGO collection. "; so I also understand both (sets and loose parts). @Nathan, is this an error? Best regards Dietmar
  13. The API-functions: GET /api/v3/lego/mocs/{set_num}/parts/ GET /api/v3/lego/sets/{set_num}/parts GET /api/v3/lego/sets/{set_num}/sets/ GET /api/v3/users/{user_token}/partlists/ GET /api/v3/users/{user_token}/setlists don't have the query-parameter "ordering" even though paging (paramter page and result with next and previous) are implemented. Is this by design? On the other hand I see that the API-function GET /api/v3/users/{user_token}/profile has a page-parameter (no ordering), but the result doesn't have the typical paging structure (count, next, previous) (Which I think makes sense when looking on what the function returns there is no paging needed). Regards Dietmar
  14. Hello Nathan, OK, I understand that. If it is a general framework behaviour, than this is clear... Than I have to find a codepoint where to implement this paging in genereal. The increase to 1000 helps in this special cae, but I see that xou can change it without any notofication (which makes sense for reacting quick on performance issues). Thank you!
  15. Completly with you! Should be remembered on a per page base (so different criteria for Lost Parts, for Set-List and Part-List)..