-
Notifications
You must be signed in to change notification settings - Fork 57
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
Start a best-practices & performance page on docs. #193
Comments
@adrianthedev I would add: defaulting searchable: true on association, to avoid gigantic SELECT. |
11 tasks
I'd suggest adding information about properly setting up STI. In particular, the need to create resources for each STI sub-type, even if the presentation of entities won't vary. |
adrianthedev
changed the title
Start a best-practices page on docs.
Start a best-practices & performance page on docs.
Apr 19, 2024
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting this from this conversation.
We need to highlight some of the things users should or shouldn't do to get more performance out of their apps.
We do that in certain sections, but an overview should be more useful.
Let's add it under the
configuration
section in the menu.Some of the things we should talk about:
include
if/else
in fieldsvisible
,disabled
, and moreOpen to more suggestions
The text was updated successfully, but these errors were encountered: