feat: adjust other handler for urlreward activity#496
feat: adjust other handler for urlreward activity#496hmcdat wants to merge 2 commits intoTheNetsky:v3from
Conversation
|
Interesting, does the flyout data contain the same data as the regular dashboard? If so, it can be used as an alternative/fallback for the dashboard data. However in this PR you're also commenting out some other things as well as generating a random hash instead of using the one from the activity itself for some reason? |
|
|
Is there any benefit gained from using this version? |
|
@JoeGarcia2 you can finish the "UrlReward" activities on new UI automatically |
|
The API works really well on the new dashboard!, But there is no data for this activity yet. 
|
|
yes, because this tool currently does not support for new UI, so no any available ways to handle quests |
- Add PanelFlyoutData interface for panel flyout API - Add getPanelFlyoutData() method to fetch from Bing panel flyout API - Update UrlReward to use new V4 API endpoint (bing.com/msrewards/api/v1/reportactivity) - Update DoubleSearchPoints and FindClippy to use mobile API with Bearer token - Skip requestToken check for V4 - Add panelData property to bot and fetch in Main flow
…rePromotions - Add flyoutResult.morePromotions lookup - Use userInfo.promotions with fallback to name field - Align with upstream V4 changes
…esult.morePromotions" This reverts commit dc486f0.
|
So this PR is specifically to comply with the new dashboard? If so it won't be for v3, but I will change this for v4. I do not have proper access to the new dash yet. But I assume none of the current methods for dashboard data work on the new dashboard. |
4 participants
In this pr, I adjusted the working way of urlreward activity by using panel flyout api, it's still working for me until now