Edit - Software Engineering Stack Exchange

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*

Rev

This approach would be closer to the option of passing the caller, but instead of using it in an if-statement calling appropriate function on it, which will let that concern be dealt with by the frontend instead, which makes more sense than religiously using exceptions. But not splitting up functions into smaller parts was also an issue for me, I have realized. In this specific example I ended up splitting the function into a title_to_id() for getting the id and handling the frontend specific logic in the frontend module, then calling remove_by_id(). This separates the logic more.

Hugo Schongin
– Hugo Schongin

2025-04-06 20:21:12 +00:00
Commented Apr 6 at 20:21

Add a comment |

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

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>

formatting help »
answering help »