Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR fixes a missing await on ChangesAsync OSM changeset parsing fix
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant Test
participant MSW
participant OsmApiClient
participant parseOsmChangeXml
Test->>MSW: stubDownload registers changeset download route
Test->>OsmApiClient: getOsmChange()
OsmApiClient->>MSW: downloadOsmChange request
MSW-->>OsmApiClient: OSM_CHANGE_XML response
OsmApiClient->>parseOsmChangeXml: await parse(xml)
parseOsmChangeXml-->>OsmApiClient: osmChange object
OsmApiClient-->>Test: parsed osmChange
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
parseOsmChangeXml(...)in both the export archive builder andOsmApiClient.getOsmChange, ensuring parsed change data is fully resolved before use.OsmApiClient.getOsmChangewith MSW, verifying the downloaded XML is parsed correctly and timestamps are normalized toDateobjects.@osmcha/osmchange-parser, declaring its async default export asparseOsmChangeXml(xmlString: string): Promise<OsmChange>.