We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So instead of
MyDataObject.HELLOWORLD
MyDataObject.db_MyField
or MyDataObject.has_one_RelationName
So we can use the same entities for generateCMSFields and Scaffolding, e.g. getFrontEndFields()
This would need a tweak in all form templates or does BedrockField::getEntity() know if it's a db_ or has_one_ field?
Would be great if we could make it switchable, so it doesn't break old code.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
So instead of
MyDataObject.HELLOWORLD
MyDataObject.db_MyField
or MyDataObject.has_one_RelationName
So we can use the same entities for generateCMSFields and Scaffolding, e.g. getFrontEndFields()
This would need a tweak in all form templates or does BedrockField::getEntity() know if it's a db_ or has_one_ field?
Would be great if we could make it switchable, so it doesn't break old code.
The text was updated successfully, but these errors were encountered: