Skip to content
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

Monitor "Livraison" side of the application #533

Open
laurentlabat opened this issue Aug 18, 2024 · 3 comments · May be fixed by #549
Open

Monitor "Livraison" side of the application #533

laurentlabat opened this issue Aug 18, 2024 · 3 comments · May be fixed by #549

Comments

@laurentlabat
Copy link

Hi,

I would like to use the tgtg-scanner to monitor when new "Livraison" packages are available.
"Livraison" is at least available in france, and offers the option to order a parcel of items (and this is sent by TGTG or by one of their supplier), but does not rely on your location.

You just need to place an order when the "parcel" is available, and this is delivered by a shipping company to your home.

Is there an option to look into that, or any idea on how to proceed to extend the current scanner or that option ?

thanks,
tgtg-livraison

@floriegl
Copy link
Contributor

In English, it's called "Delivery" and it looks like it's available in multiple countries. I would say the main question would be how the delivery items should be handled. As you can't favorite them, you can only check for all at once.

  • Does it make sense to send out a notification whenever a new delivery item gets added and/or gets available again?
  • How would the monitor store the delivery items where a notification already got sent out? If you store them forever, it could lead to an issue with storage. And not saving them would lead to the issue, that all notifications get sent again after a bot restart...

@laurentlabat
Copy link
Author

laurentlabat commented Sep 12, 2024 via email

@floriegl
Copy link
Contributor

This also duplicates #529 as I have just noticed

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 a pull request may close this issue.

2 participants