-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added documentation for fields with alternate display modes. #17333
Conversation
Thank you for submitting your first pull request, awesome! 🚀 If you haven't already, please take a moment to review our contribution guide. This guide provides helpful information to ensure your contribution aligns with our standards. A core team member will review your pull request. If you like Orchard Core, please star our repo and join our community channels. |
@dotnet-policy-service agree company="Techstension LLC" |
Co-authored-by: Zoltán Lehóczky <[email protected]>
Co-authored-by: Zoltán Lehóczky <[email protected]>
Congratulations on your first PR merge! 🎉 Thank you for your contribution! We're looking forward to welcoming other contributions of yours in the future. @all-contributors please add @jeff-techstension for code. If you like Orchard Core, please star our repo and join our community channels. |
@github-actions[bot] I've put up a pull request to add @jeff-techstension! 🎉 |
The requirements for using the placement module or the placement.json file is stricter when using a content field with a display mode other than standard. I updated the documentation to include the rules as I understand them.
Fix #17328