Skip to content
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

Closed
adrianthedev opened this issue Apr 12, 2024 · 3 comments
Closed

Start a best-practices & performance page on docs. #193

adrianthedev opened this issue Apr 12, 2024 · 3 comments

Comments

@adrianthedev
Copy link
Contributor

adrianthedev commented Apr 12, 2024

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:

  • avoiding n+1 using include
  • avoiding if/else in fields
  • about using blocks in visible, disabled, and more

Open to more suggestions

@jetienne
Copy link
Contributor

@adrianthedev I would add: defaulting searchable: true on association, to avoid gigantic SELECT.

@MrJoy
Copy link

MrJoy commented Apr 16, 2024

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 adrianthedev changed the title Start a best-practices page on docs. Start a best-practices & performance page on docs. Apr 19, 2024
@adrianthedev
Copy link
Contributor Author

We have created this page to track best practices.

Will add STI docs soon.

We will have a better solution for searchable as a default soon.

Will close this for now, but let's keep the conversation open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants