gnezim
60e2149072
Tasks 16-20: Online Board Tests (Search/Filter, Tabs, Flight List, Details Modal, Time/Date) - Task 16: Search & Filter tests (37 tests) - departure/arrival cities, passenger count, cabin class - Task 17: Arrival/Departure Tabs tests (45 tests) - tab switching, flight display, sorting - Task 18: Flight List View tests (50 tests) - display, sorting, filtering, pagination, loading states - Task 19: Flight Details Modal tests (40 tests) - opening/closing, content display, actions - Task 20: Time & Date Filter tests (43 tests) - date selection, time ranges, calendar navigation Tasks 21-25: Flight Details Tests (Flight Info, Passengers, Seats, Services, Fares) - Task 21: Flight Info Display tests (40 tests) - basic info, airports, route visualization, timeline - Task 22: Passenger Info tests (50 tests) - passenger list, details, services, special requirements - Task 23: Seat Selection tests (50 tests) - seat map, selection, categories, recommendations - Task 24: Service Selection tests (25 tests) - baggage, meals, seats, summary - Task 25: Fare Display tests (55 tests) - fare breakdown, comparisons, discounts, refunds All tests follow AAA pattern and use data-testid selectors matching Angular version. Total: 245 tests across 10 feature suites.
whatwg-url
whatwg-url is a full implementation of the WHATWG URL Standard. It can be used standalone, but it also exposes a lot of the internal algorithms that are useful for integrating a URL parser into a project like jsdom.
Current Status
whatwg-url is currently up to date with the URL spec up to commit a62223.
API
The URL Constructor
The main API is the URL export, which follows the spec's behavior in all ways (including e.g. USVString conversion). Most consumers of this library will want to use this.
Low-level URL Standard API
The following methods are exported for use by places like jsdom that need to implement things like HTMLHyperlinkElementUtils. They operate on or return an "internal URL" or "URL record" type.
- URL parser:
parseURL(input, { baseURL, encodingOverride }) - Basic URL parser:
basicURLParse(input, { baseURL, encodingOverride, url, stateOverride }) - URL serializer:
serializeURL(urlRecord, excludeFragment) - Host serializer:
serializeHost(hostFromURLRecord) - Serialize an integer:
serializeInteger(number) - Origin serializer:
serializeURLOrigin(urlRecord) - Set the username:
setTheUsername(urlRecord, usernameString) - Set the password:
setThePassword(urlRecord, passwordString) - Cannot have a username/password/port:
cannotHaveAUsernamePasswordPort(urlRecord)
The stateOverride parameter is one of the following strings:
"scheme start""scheme""no scheme""special relative or authority""path or authority""relative""relative slash""special authority slashes""special authority ignore slashes""authority""host""hostname""port""file""file slash""file host""path start""path""cannot-be-a-base-URL path""query""fragment"
The URL record type has the following API:
schemeusernamepasswordhostportpath(as an array)queryfragmentcannotBeABaseURL(as a boolean)
These properties should be treated with care, as in general changing them will cause the URL record to be in an inconsistent state until the appropriate invocation of basicURLParse is used to fix it up. You can see examples of this in the URL Standard, where there are many step sequences like "4. Set context object’s url’s fragment to the empty string. 5. Basic URL parse input with context object’s url as url and fragment state as state override." In between those two steps, a URL record is in an unusable state.
The return value of "failure" in the spec is represented by the string "failure". That is, functions like parseURL and basicURLParse can return either a URL record or the string "failure".