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

Coding style guide #730

Open
rubenthoms opened this issue Sep 18, 2024 · 0 comments
Open

Coding style guide #730

rubenthoms opened this issue Sep 18, 2024 · 0 comments
Assignees
Labels
question Further information is requested

Comments

@rubenthoms
Copy link
Collaborator

rubenthoms commented Sep 18, 2024

Basic styleguide: https://ts.dev/style/

However, the styleguide is not describing every use-case. There are some topics where we might want to differ. Feel free to add points to the list.

Functions

  • Named functions vs. arrow functions: when is it ok (debugging info) to use arrow functions and when should we definitely use named functions (e.g. return functions of useEffect) - what is the complexity/length threshold? -> arrow functions when one-liners, binding this context, and expressions
@rubenthoms rubenthoms added the question Further information is requested label Sep 18, 2024
@github-project-automation github-project-automation bot moved this to Backlog 📝 in Webviz Sep 18, 2024
@rubenthoms rubenthoms changed the title Discussion: Coding style guidelines Coding style guide Oct 31, 2024
@anders-kiaer anders-kiaer pinned this issue Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Backlog 📝
Development

No branches or pull requests

6 participants