LAD / LOD extensions for B records

[spasutto]

example :

    I013637LAD
    B1526594446200N00547906EA013770137247

source : https://www.fai.org/sites/default/files/igc_fr_specification_with_al8_2023-2-1_0.pdf

Lat/Long - D D M M m m m N D D D M M m m m E
DD - Latitude degrees with leading 0 where necessary
DDD - Longitude degrees with leading 0 or 00 where necessary
MMmmmNSEW - Lat/Long minutes with leading 0 where necessary, 3 decimal places of minutes are mandatory,
followed by N, S, E or W as appropriate. If additional digits are used, for the fractional minutes define the positions
through codes LAD and LOF in the I record.

[Turbo87]

can you add a few tests to make sure it works as expected and will not regress in the future? 🙏

[spasutto]

Hello, I slightly modified the commit code (no more impact on parseLatitude function) and added IGC Sample/associated tests.
Let me now if the code/tests needs revisions 👍

[spasutto]

Note 1 : the code directly regex test the extension :
RE_INT.test(extensions['LAD'])
Even if there isn't 'LAD' extension.
I've tested this snippet without the extension it return false so I assume there's no need to test on presence in extensions but I can strengthen if you want !

Note 2 : the extension parsing block was simply moved (without modification) above the lat/lon parsing (where LAD/LOD extensions are needed).

[Turbo87]

thanks :)

[spasutto]

Sorry I'm not familiar with Jest, I've added the test in the snapshot file, I hope that will solve the workflow problem