Bug report: /budgets/last-used/settings errors with resource_not_found

Most endpoints support `last-used` as a budget ID, but `/budgets/<budget-id>/settings` doesn't seem to.  It works fine if I specify an actual budget ID.

Expected result:

$ curl -H "Authorization: Bearer REDACTED" https://api.youneedabudget.com/v1/budgets/last-used/settings
{"data":{"settings":{"date_format":{"format":"YYYY-MM-DD"},"currency_format":{"iso_code":"CAD","example_format":"123,456.78","decimal_digits":2,"decimal_separator":".","symbol_first":true,"group_separator":",","currency_symbol":"$","display_symbol":true}}}}

Actual result:

$ curl -H "Authorization: Bearer REDACTED" https://api.youneedabudget.com/v1/budgets/last-used/settings
{"error":{"id":"404.2","name":"resource_not_found","detail":"Resource not found"}}

Note that this does work:

$ curl -H "Authorization: Bearer REDACTED" https://api.youneedabudget.com/v1/budgets/deadbeef0fab2cd9-3a7f-8254-c925-92581bf3ca72/settings
{"data":{"settings":{"date_format":{"format":"YYYY-MM-DD"},"currency_format":{"iso_code":"CAD","example_format":"123,456.78","decimal_digits":2,"decimal_separator":".","symbol_first":true,"group_separator":",","currency_symbol":"$","display_symbol":true}}}}
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 12 days agoLast active
  • 36Views
  • 1 Following