Allow more options to the Apollo Server config

[abdonrd]

Description of what you did:

Allow more options to the Apollo Server config

[alexandrebodin]

Yeah sth like that would allow to pass any param the users want. In v4 we can break the config to have a apolloServerConfig key to make it cleaner :)

[alexandrebodin]

sth wrong with the tests :)

[alexandrebodin]

this will need a doc update before we can merge and a deprecation warning :)

[abdonrd]

@alexandrebodin all updated! 🚀

How would you want to add a deprecation warning?

[codecov]

Codecov Report

Merging #7665 into master will increase coverage by 0.03%.
The diff coverage is 63.63%.

@@            Coverage Diff             @@
##           master    #7665      +/-   ##
==========================================
+ Coverage   27.16%   27.20%   +0.03%     
==========================================
  Files        1163     1164       +1     
  Lines       15518    15517       -1     
  Branches     2410     2410              
==========================================
+ Hits         4216     4221       +5     
+ Misses       9534     9528       -6     
  Partials     1768     1768              

Flag	Coverage Δ
#front	19.36% <63.63%> (+0.04%)	⬆️
#unit	53.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...in/src/components/LeftMenu/LeftMenuFooter/index.js	33.33% <0.00%> (-33.34%)	⬇️
...rc/containers/EditViewDataManagerProvider/index.js	0.00% <0.00%> (ø)
.../admin/src/components/ComponentIconPicker/index.js	0.00% <0.00%> (ø)
...agerProvider/utils/retrieveComponentsFromSchema.js	68.75% <ø> (ø)
...rapi-plugin-upload/admin/src/translations/index.js	0.00% <ø> (ø)
...ovider/utils/getFieldsActionMatchingPermissions.js	100.00% <100.00%> (ø)
...ditViewDataManagerProvider/utils/tests/testData.js	100.00% <100.00%> (ø)
...rc/containers/InputModalStepperProvider/reducer.js	68.33% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5364191...e59d214. Read the comment docs.

[alexandrebodin]

@derrickmehaffy can you help @abdonrd to update the graphql doc with a deprecation warning for those old params

[alexandrebodin]

@alexandrebodin all updated! 🚀

How would you want to add a deprecation warning?

I think we should remove the old keys from the default config. and if the user sets them display a warning with strapi.log.warn()

[derrickmehaffy]

@alexandrebodin @abdonrd sure, we are just moving the tracing one right?

[abdonrd]

@alexandrebodin @abdonrd sure, we are just moving the tracing one right?

Yeah!

[derrickmehaffy]

Would be best to just adjust the documentation and move this into a major release and throw the warning in the migration guide. It's small, and the number of people actually using the tracing feature should be very low as it decreases the performance of GraphQL quite a lot.

If you want to write something up here @abdonrd I'll just ensure it gets added to the next migration guide.

@alexandrebodin did we have a planned date for v3.2.x ?

[abdonrd]

@derrickmehaffy Done!

[derrickmehaffy]

Reminder to myself when we start looking at redoing the docs, this entire GraphQL documentation needs to be rewritten x_x

[derrickmehaffy]

LGTM on the docs side, pending review from Alex on the code side

[abdonrd]

Thanks again for the review @alexandrebodin! It should work now!