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.
Required fields*
-
What a complete and detailed explanation @candied_orange, Thank you very much for that. I'll have to read it carefully more than once because I'm exhausted today, but I appreciate your time. I'll wait a little to see if more answers arrive before marking it as correct :)Diego Perez– Diego Perez2022-07-22 16:49:34 +00:00Commented Jul 22, 2022 at 16:49
-
BTW @candied_orange, and talking about DI, should I always inject an Interface instead of the actual class?Diego Perez– Diego Perez2022-07-22 17:13:59 +00:00Commented Jul 22, 2022 at 17:13
-
That's worthy of it's own question.candied_orange– candied_orange2022-07-22 17:16:34 +00:00Commented Jul 22, 2022 at 17:16
-
I have read your answer again and it is just a great answer @candied_orange. Thanks again for your time, and I'll ask the one regarding interfaces in another question.Diego Perez– Diego Perez2022-07-22 19:14:59 +00:00Commented Jul 22, 2022 at 19:14
-
Given your answer @candied_orange, I'll use my ExceptionHandler (given in the example) as a static class and AppSettings (with context + singleton database + app configuration) as Hilt ApplicationClass. I also guess Repository should be injected, because functions could change, the same for services. I understand that using DI or static classes depend on the context, and can be mixed in a project with no problems, I understand that if you use DI, this doesn't mean all your classes must be injected. One last thing, could you edit my post with a possible solution to the problem I describe.ThanksDiego Perez– Diego Perez2022-07-22 19:21:13 +00:00Commented Jul 22, 2022 at 19:21
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