🧑‍💻 linting 위반사항 수정

[mingi3314]

---

Generated summary (powered by Graphite)

TL;DR

This pull request improves error handling by chaining exceptions to provide more context when an error occurs. It also removes unnecessary __init__ methods from abstract base classes.

What changed

1. In pyrb/controllers/api/main.py, the get_default_account function now raises an HTTPException with the original InitializationError attached for context.
2. In pyrb/repositories/brokerages/base/fetcher.py, pyrb/repositories/brokerages/base/order_manager.py, and pyrb/repositories/brokerages/base/portfolio.py, the unnecessary __init__ methods were removed from the abstract base classes.
3. In pyrb/repositories/brokerages/ebest/client.py, the _raise_for_status method now raises an Exception with the original HTTPError attached for context.
4. In pyrb/repositories/brokerages/ebest/order_manager.py, the place_order method now raises an OrderPlacementError with the original HTTPError attached for context.

How to test

1. Run the application and make a request to the get_default_account endpoint. If an InitializationError occurs, the response should now include the original error message.
2. Test the abstract base classes to ensure they still function correctly without the __init__ methods.
3. Make a request that triggers an HTTPError in the pyrb/repositories/brokerages/ebest/client.py file. The error message should now include the original error message.
4. Make a request that triggers an HTTPError in the pyrb/repositories/brokerages/ebest/order_manager.py file. The error message should now include the original error message.

Why make this change

Chaining exceptions provides more context when an error occurs, which can help with debugging. Removing unnecessary __init__ methods from abstract base classes makes the code cleaner and easier to read.

[mingi3314]

Current dependencies on/for this PR:

• main
  • PR 🎨 ruff integration #83
    • PR 🧑‍💻 linting 위반사항 수정 #84 👈

This stack of pull requests is managed by Graphite.

[mingi3314]

Merge activity

• Feb 18, 9:31 AM EST: @mingi3314 started a stack merge that includes this pull request via Graphite.
• Feb 18, 9:32 AM EST: Graphite rebased this pull request as part of a merge.
• Feb 18, 9:33 AM EST: @mingi3314 merged this pull request with Graphite.