fix: handle properly null and undefined props values

[marcuspoehls]

🔗 Linked issue

I didn’t create an issue and instead provide a failing test.

❓ Type of change

• 📝 Test to reproduce an issue
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I’m running into Cannot read properties of undefined (reading 'Symbol(ignoreFirstLoad)') if a response prop is null or undefined. We allow props having string | undefined values and currently this fails because the code always assumes a value.

I provided a failing test to reproduce the issue.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[marcuspoehls]

The issue is in src/inertia.ts https://github.com/adonisjs/inertia/blob/ee11d9bcfd9a90c0c845bae278f92856ee351a71/src/inertia.ts#L106C56-L106C66.

@Julien-R44 Julien, I’m not sure how you like to handle null and undefined props. The value in the linked line should handle nullish props. You may add a check as you’re more into the code. Otherwise I could edit the mentioned line and add checks.

[Julien-R44]

Thanks for the failing test !

Yeah, I think that props should be returned even if they are null or undefined

[marcuspoehls]

@Julien-R44 thank you for taking this pull request over making the adjustments. And also thank you for a new release 🫶

[marcuspoehls]

@Julien-R44 I can confirm that our app works as expected again with nullish props in @adonisjs/inertia:2.x 🙂 thank you!