You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
13 is bad, 4 is worse (seriously, Auth0 is wonderful). Keeping everything on the server side is a much better experience and encapsulates the fact that you're using an API call to Auth0, which at the answer suggests, might change to being a cached representation in the future.mgw854– mgw8542016-12-05 16:20:13 +00:00Commented Dec 5, 2016 at 16:20
-
Thanks both for the well explained answer/comment. I'm still doubting between option 1 and 2. On first thought option 1 (Repository) will be better if there is need to join internal and Management API tables or that the Management API result needs more complex manipulation and option 2 (Web API) will be beter if the Management API results are mostly used straightaway without the need of manipulating (ex: show all users). I guess this will be different for all projects.Sam– Sam2016-12-06 08:11:44 +00:00Commented Dec 6, 2016 at 8:11
-
1That choice is more difficult to get it right when looking from the outside without knowing all the little details of a specific project; In the end you should go with the one you feel most comfortable and is less complex. Since it's on the server-side, even if you get it wrong at first it's easier to refactor.João Angelo– João Angelo2016-12-06 08:39:57 +00:00Commented Dec 6, 2016 at 8:39
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you