When designing an API for your Application Frontend, what is your rule of thumb?
For further actions, you may consider blocking this person and/or reporting abuse
When designing an API for your Application Frontend, what is your rule of thumb?
For further actions, you may consider blocking this person and/or reporting abuse
Dev Lawrence -
Thomas Sentre -
Todd Sharp -
Anuradha Aggarwal -
Once suspended, decker67 will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, decker67 will be able to comment and publish posts again.
Once unpublished, all posts by decker67 will become hidden and only accessible to themselves.
If decker67 is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to decker.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag decker67:
Unflagging decker67 will restore default visibility to their posts.
Top comments (8)
These are some rules i apply that may not suit everyone:
Make it save for ways you dont think about in the first way.
Don't make me think.
Keep it consistent. (Used patterns and naming)
Don't make the frontend do the data processing.
Do one task, and do it right, don't overthink it.
If you want a rule that's less verbal and more technical, refer to SOLID principles.
Make it functional not technical, because the underlying technic can change more often than the desired function.
Use the Open API standard with Swagger to simplify documentation and allow developers and users to work with it in a meaningful way.
Modularity. Each part has its own resposaility (easy to maintain)