Standardize child passenger indicator to isChild

[Copilot]

Two property names (child and isChild) were used interchangeably to flag child passengers, causing inconsistency between the search/price path and the booking path.

Changes

• convert-passengers-object-to-array.js — rename child → isChild, drop // quickfix comment
• AIR_PRICE_REQ, AIR_AVAILABILTIY_REQUEST, AIR_LOW_FARE_SEARCH_REQUEST templates — update {{#if child}} → {{#if isChild}}
• convert-passengers-object-to-array.test.js — update assertions to match

// Before
list.push({ ageCategory, child: (ageCategory === 'CNN') }); // quickfix

// After
list.push({ ageCategory, isChild: (ageCategory === 'CNN') });

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Which way to indicate child? isChild or child?</issue_title>
<issue_description>There's two way to indicate a passenger is a children,

in Air/Services/transformer/add-meta-passengers-booking.js

      item.isChild = true;

in Air/Services/transformer/convert-passengers-object-to-array.js

          child: (ageCategory === 'CNN'), // quickfix

This makes really confusing, to them or to implement other features. Can you sort them out? </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Which way to indicate child? isChild or child? #428

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud