[3.0.x] Updates Custom Field Constructor Documentation (backport #12892) by @RommelTJ #13124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
Helpful things
Fixes
Fixes #5172
Purpose
Updates the Custom Field Constructor documentation to be more clear. Provides suggested filenames and directories so that a beginner can get started with creating custom field constructors.
If anything is still not clear, or we need further edits, let me know. I'm happy to make them.
Background Context
Outstanding issue with the documentation since October 2015. I created a minimal ("Hello Play") sample project with a minimal custom field constructor to verify the approach.
References
#5172
This is an automatic backport of pull request #12892 done by [Mergify](https://mergify.com).