Skip to content

feat: aggregating checkLocationWorkerRoute #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

Tsuk1ko
Copy link

@Tsuk1ko Tsuk1ko commented Jul 7, 2024

自测正常,最好再试试

close #46

@lyc8503 lyc8503 force-pushed the main branch 3 times, most recently from f4d8580 to be832b0 Compare August 22, 2024 04:39
@lyc8503
Copy link
Owner

lyc8503 commented Apr 11, 2025

checkLocationWorkerRoute 正在大改版成新的 checkProxy 功能,这个 PR 暂时先 close 了,后续如果用到你的代码的话会直接在 commit 时 co-author 你(主要应该会用迁移到 D1 相关的代码,我要先在自己的实例上测试一段时间)。

无论如何十分感谢你的贡献~

@lyc8503 lyc8503 closed this Apr 11, 2025
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


checkLocationWorkerRoute is being revamped into the new checkProxy function. This PR is closed for the time being. If you use your code in the future, you will directly co-author you when commit (mainly, you should use the code related to migration to D1. I want to test it on my own instance for a while).

Thank you very much for your contribution anyway~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

建议:聚合 checkLocationWorkerRoute 请求以减少 worker 请求数及使用 Cloudflare D1 存储数据
3 participants