docs: clarify app.config.*s files are supported

[DoctorJohn]

Description

This PR clarifies that app.config.js and app.config.ts files are still supported (just like app.json files).

This PR complements the app.json config examples with app.config.js and app.config.ts examples.

I was hoping we would not have to do this since it's somewhar cluttering the docs, but I tried to compensate that by using docs.page accordion components. Also tried using nested tabs, but they don't appear to be supported (i.e. they don't render correctly).

Related issues

• [🐛] No signature of method: java.lang.Boolean.getStringValue() under android v14.1.0+ #620
  Hope this helps with issues like this, where some people got the impression that app.config.*s support was dropped

Test Plan

• Validate the changes via the docs preview

[docs-page]

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/react-native-google-mobile-ads~625

Documentation is deployed and generated using docs.page.

[dylancom]

Hmm I am a bit unsure if we need to add all this.

[DoctorJohn]

Hmm I am a bit unsure if we need to add all this.

After sleeping another night over it I think the same. It shouldn't be our job to teach users about three different ways to create an expo config file. I'll remove the accordions and app.config.*s examples again and instead only mention the support for app.config.*s and maybe refer users to the expo docs. Does that sound good @dylancom ?

[dylancom]

Sounds good @DoctorJohn !

[mikehardy]

🎉 This PR is included in version 14.2.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀