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.
2.3 KiB
2.3 KiB
v2.0.1 (Mar 29, 2021)
IMPORTANT: Security Fix
This version contains an important security fix. If you are using netmask
<=2.0.0, please upgrade to2.0.1or above.
- Rewrite byte parsing without using JS
parseInt()(commit)- This is CVE-2021-29418.
Bugfixes
- Add checks on spaces before and after bytes
- This will now throw an exception when spaces are present like ' 1.2.3.4' or '1. 2.3.4' or '1.2.3.4 '.
Internal Changes
- Avoid some useless memory allocations
- New Mocha testing suite, thanks @kaoudis #36
v2.0.0 (Mar 19, 2021)
Breaking Change
Previous API was treating IPs with less than for bytes as IP with a netmask of the size of the provided bytes (1=8, 2=16, 3=24) and was interpreting the IP as if it was completed with 0s on the right side.
Proper IP parsing for these is to consider missing bytes as being 0s on the left side.
Mask size is no longer infered by the number of bytes provided.
This means that the input 216.240 will no longer be interpreted as 216.240.0.0/16, but as 0.0.216.240/32,
as per convention.
See the change.
Bugfixes
- Fix improper parsing of hex bytes
v1.1.0 (Mar 18, 2021)
IMPORTANT: Security Fix
This version contains an important security fix. If you are using netmask
<=1.0.6, please upgrade to1.1.0or above.
- Fix improper parsing of octal bytes (commit)
- This is CVE-2021-28918.
- See also the npm advisory
Other Changes
- Performance: Avoid large allocations when provided large netmasks (like
/8)- Thanks @dschenkelman #34
v1.0.6 (May 30, 2016)
- Changes before this release are not documented here. Please see the commit list or the compare view.