fix(a380/mfd): FLT NBR is now displayed as a mandatory input field

[jet2code]

Fixes #9752

Summary of Changes

• Set atcCallsign's initial value to null to ensure it met the criteria for displaying mandatory boxes in InputField
• This displays the FLT NBR input field as mandatory. CPNY RTE was left as is as it is currently a disabled field.

Screenshots (if necessary)

References

Additional context

Discord username: john.xyz

Testing instructions

1. Open the INIT page
2. Ensure FLT NBR has mandatory input symbology

How to download the PR for QA

Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, find and click on the PR Build tab
4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

[flogross89]

Good spot, thanks. Do you happen to have a reference image showing the A380 FMS? Yours shows an A350.

[jet2code]

Good spot, thanks. Do you happen to have a reference image showing the A380 FMS? Yours shows an A350.

The reference was from the issue that was posted so I am not sure but I did confirm a reference from the A380 here. I will update the changelog as soon as possible.

image

[flogross89]

Ah, and one more thing. If atcCallsign is null, the callsign in the upper right should display the dashes instead of being blank.
You need to change this in AbstractHeader.tsx, line 111:
{this.props.callsign} to {this.props.callsign.map((cs) => (cs !== null ? cs : '---------'))}

[jet2code]

Ah, and one more thing. If atcCallsign is null, the callsign in the upper right should display the dashes instead of being blank.

You need to change this in AbstractHeader.tsx, line 111:

{this.props.callsign} to {this.props.callsign.map((cs) => (cs !== null ? cs : '---------'))}

Yeah, I did notice this in the video I sent. I'll get that detail in as well.

[jet2code]

Just pushed the latest changes.

[flogross89]

@jet2code Looking good now, thanks! If you're done with changes you can always ping me or re-request a review so that I'll be notified. Otherwise, there's the risk of me missing updates, because so many PRs are open right now :)
I'm going to merge this PR without QA, as the risk of the changes are manageable. Thanks for the contribution!

[flogross89]

@jet2code I overlooked something in the review, which broke the callsign display in the upper right of the MFD (tried to render [object object] as string. Here's the PR for the fix, nothing else to be done: #9814