7 Commits

Author	SHA1	Message	Date
Mark Ferrell	04a533aec9	feat: leverage go's mod replace sanely ... The Proton-API-Bridge should not be attempting to take over, nor re-define, the existing proton-go-api interfaces. This is known has an "unfriendly fork" and increases the overall complexity of maintaining the Proton-API-Bridge. All changes to the proton-go-api should be done as "friendly" as possible, and should be submitted back upstream for inclusion. This improves the functionality of the proton-go-api for more than just 1 project, and it reduces the long-term maintenance required for Proton-API-Bridge. To this end, Proton-API-Bridge should be written to always assume it is using github.com/ProtonMail/proton-go-api and leverage the `replace` operation in go.mod in order to leverage our "friendly fork" of proton-go-api. I.e. the long-term goal should be to _not_ maintain a fork of proton-go-api. > Anything else would be uncivilized.	2025-01-16 05:38:50 -08:00
Chun-Hung Tseng	bc9415009f	Select the address key according to the email address recorded at Link	2023-09-08 08:51:06 +02:00
Chun-Hung Tseng	cedf21b695	Replace disableCaching with enableCaching	2023-07-16 06:06:16 +02:00
Chun-Hung Tseng	d7a4545314	Implemented complete caching mechanism	2023-07-15 21:19:03 +02:00
Chun-Hung Tseng	4924a926d6	Add insert kr to cache	2023-07-15 21:19:02 +02:00
Chun-Hung Tseng	d293198b51	Add insert link to cache ... Add DisableLinkCaching config	2023-07-15 21:19:02 +02:00
Chun-Hung Tseng	e330ee8276	Refactor GetLink in preparation for caching	2023-07-15 21:19:02 +02:00