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

Fix: collections pagination and other admin UX improvements #156

Merged
merged 2 commits into from
Apr 22, 2024

Conversation

polishq
Copy link
Contributor

@polishq polishq commented Apr 19, 2024

What problem is this solving?

Solves the problem where the collections tab of the admin organization details page does not allow pagination through the available collections (although the ##-## of ## text would change, the actual list of collections would never change). Also solves the problem where the initial collections query did not set any pageSize variable, resulting in only 20 records being returned. Also removes the option to show 100 collections per page, as the API allows a maximum of 50 to be returned at once.

This PR also adds loading indicators to the admin organization details page, in the following tabs: cost centers, collections, payment terms, price tables, and sellers.

How to test it?

New version linked here: https://arthur--cosmorentals.myvtex.com/admin/b2b-organizations/organizations/7f7780af-dbfe-11ee-8452-0ecf4a7e9b55/#/collections

Note that you can successfully paginate through the available collections.

Copy link

vtex-io-ci-cd bot commented Apr 19, 2024

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link

vtex-io-docs-bot bot commented Apr 19, 2024

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

Copy link

Messages
📖 ❤️ Thanks!
📖

🎉 PR additions = 41, PR deletions = 24

Generated by 🚫 dangerJS against 7da8b93

@polishq polishq requested a review from ArthurTriis1 April 19, 2024 20:57
Copy link

!collectionsData?.collections?.items?.length ||
collectionOptions.length
) {
if (!collectionsData?.collections?.items?.length) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: could you explain why this line was changed? Why the check on collectionOptions.lenght was removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The effect of this check is that it's impossible to advance to the next page of available collections. The code sees that collectionOptions already has length (the first page of results) and therefore skips setting the second page of results to state.

@polishq polishq merged commit 8a1decc into master Apr 22, 2024
14 checks passed
@polishq polishq deleted the fix/admin-loading-pagination branch April 22, 2024 12:25
Copy link

vtex-io-ci-cd bot commented Apr 22, 2024

Your PR has been merged! App is being published. 🚀
Version 1.31.2 → 1.31.3

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

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.

2 participants