Open diogofonte opened 1 year ago
@CarlosMealha @diogofonte any updates on this?
@CarlosMealha @diogofonte any updates on this?
We were waiting for opinions about the divs that are causing extra space in mobile view search, but the button "show hidden offers" is ready. This is not the not the principal objective of this PR, but the problem affects directly our issue.
@CarlosMealha @diogofonte any updates on this?
Also, is there any endpoint responsible to fetch hidden offers or we need to filter the offers in order to specify them ?
@CarlosMealha @diogofonte any updates on this?
Also, is there any endpoint responsible to fetch hidden offers or we need to filter the offers in order to specify them ?
the GET /offers
endpoint already handles this: you need to pass a query value named showHidden
, if I recall correctly, and set it to true
in order to see hidden offers (if you have permission to do so of course).
If you are asking in the context of this PR, the feature that needs to be implemented is the possibility for admins to pass that showHidden
value, which is currently not possible. Maybe I misunderstood your question.
@CarlosMealha @diogofonte any updates on this?
We were waiting for opinions about the divs that are causing extra space in mobile view search, but the button "show hidden offers" is ready. This is not the not the principal objective of this PR, but the problem affects directly our issue.
I think I looked around a while ago and recall this being an issue in the MultiOptionAutocomplete component, not that one, but i might be wrong. If the problem is in the component you showed maybe you could replace the React Fragment (the <></>
thing) with null
and see if it works.
@CarlosMealha @diogofonte any updates on this?
Also, is there any endpoint responsible to fetch hidden offers or we need to filter the offers in order to specify them ?
the
GET /offers
endpoint already handles this: you need to pass a query value namedshowHidden
, if I recall correctly, and set it totrue
in order to see hidden offers (if you have permission to do so of course).If you are asking in the context of this PR, the feature that needs to be implemented is the possibility for admins to pass that
showHidden
value, which is currently not possible. Maybe I misunderstood your question.
Yes, my question was about the endpoint specifically, and your answer cleared my doubts. Thank you!
Okay, me and Diogo made the show hidden toggle on admin account working properly
Since there is no backend to test this (at the moment), please include a small video demonstrating this feature.
Also, beware of the upstream changes, you'll need to rebase this branch with develop later.
Patch coverage: 70.37
% and project coverage change: -0.21
:warning:
Comparison is base (
e2c6463
) 89.05% compared to head (5626b67
) 88.84%.:exclamation: Current head 5626b67 differs from pull request most recent head 1d046e2. Consider uploading reports for the commit 1d046e2 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Codecov Report
Base: 88.98% // Head: 88.96% // Decreases project coverage by
-0.03%
warningCoverage data is based on head (
6e15449
) compared to base (5f96cb4
). Patch coverage: 85.71% of modified lines in pull request are covered.mega This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files
umbrella View full report at Codecov. loudspeaker Do you have feedback about the report comment? Let us know in this issue.
We will take care of this as the feature for the related showHidden URL filter are still in progress and the corresponding tests
Now the showHidden attribute is present in the URL
Video demonstrating the final result:
I'll leave the code review for the others but I think the result looks neat!
We noticed that it was not possible to reset the show hidden offers field with the button "reset advanced fields". Now it's possible.
Video:
Now the showHidden attribute is present in the URL
Video demonstrating the final result:
~This looks awesome, great job. I just had an idea: perhaps we should completely remove the showHidden
field from the URL if it is not present. Since this is an admin only thing, its a little bit of "secrecy" (in lack of a better term) we had to this feature. Not mandatory tho, this is great as it is. What do you think @CarlosMealha @diogofonte @BrunoRosendo~
I just now saw that this was tackled in the video following, ignore this comment.
Now the showHidden attribute is present in the URL Video demonstrating the final result:
~This looks awesome, great job. I just had an idea: perhaps we should completely remove the
showHidden
field from the URL if it is not present. Since this is an admin only thing, its a little bit of "secrecy" (in lack of a better term) we had to this feature. Not mandatory tho, this is great as it is. What do you think @CarlosMealha @diogofonte @BrunoRosendo~I just now saw that this was tackled in the video following, ignore this comment.
Yes, we changed it to follow the flow already implemented. We need to see what's going wrong with the tests and we think that after that it is ready to close and merge.
Also, don't forget to rebase.
Closes #236