Skip to content

Commit 9a768ea

Browse files
committed
guide-agent-on-non-intuitive-aspects-of-the-codebase
1 parent 86c2782 commit 9a768ea

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

agents.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,16 @@ Each agent file starts with a "Read the overview" links block to the relevant `d
4242
Each relevant `docs/**` page gets a small footer: "For implementation details, see `<path>/agents.md`".
4343

4444
Reduce code/text duplication as much as possible across twin docs and agents files.
45+
46+
## Guidance on development
47+
48+
### spendee_api.py is deprecated
49+
50+
It is left there if anytime a function would be needed from it, but all development happens on the firebase implementation, just as the core spendee developers did.
51+
52+
### Do not modify login flow or authentication
53+
54+
The authentication in the firebase_client.py is not intuitive, you may used to have more seamless firebase authentication, but THIS WORKS, DO NOT MODIFY. I was not able to make it work using the google.oauth2.credentials, do not try re-implementing that. Maybe because web page flow was only enabled by original authors and service owners, and python SDK based auth flow differs. Maybe because that library is intended for admin API access, not user-client access, I am not an expert in this, but did considerable trial-and-error on that front.
55+
56+
57+
If you face authorization problems, troubleshoot what identities and wallets are used, or you may experiment with new firebase centric functions, but the authentication steps in the login flow should be only modified if user approved or explicitly asked.

0 commit comments

Comments
 (0)