Show users their own resources

[Emmanuel-Dominic]

This is a:

• [x] ✨ New feature - new behaviour has been implemented
• [ ] 🐛 Bug fix - existing behaviour has been made to behave
• [ ] ♻️ Refactor - the behaviour has not changed, just the implementation
• [ ] ✅ Test backfill - tests for existing behaviour were added but the behaviour itself hasn't changed
• [ ] ⚙️ Chore - maintenance task, behaviour and implementation haven't changed

Description

• [x] When you log into the application while you have published resources, navigate to the accounts page to view your personal resources, while as an administrator, you will see your personal published and draft resources.

• [x] Users are able to view their published resources when logged in as normal authenticated users while admins can also see draft resources.

• Purpose -

• [x] Users can see the resources they suggested without having to search through the entire list of resources in the application.

• How to check -

• [x] Login into the application.

• [x] Write some suggestions to be published yet if you have logged in as an admin

• [x] If you're an admin, you will be able to see a list of your published resources as well as your draft resources on the account page.

• [x] If you're a normal authenticated user, you will see only the published resources.

  Links

• [x] resolve #12

Author checklist

• [x] I have written a title that reflects the relevant ticket
• [x] I have written a description that says what the PR does and how to validate it
• [x] I have linked to the project board ticket (and any related PRs/issues) in the Links section
• [x] I have added a link to this PR to the ticket
• [x] I have made the PR to main from a branch named feature/show-users-resource
• [x] I have manually tested that the app still works correctly
• [x] I have requested reviewers here and in my team chat channel
• [ ] I have spoken with my PM or TL about any parts of this task that may have become out-of-scope, or any additional improvements that I now realise may benefit my project
• [x] I have added tests, or new tests were not required
• [x] I have updated any documentation (e.g. diagrams, schemas), or documentation updates were not required

[Emmanuel-Dominic]

Hello @textbook, Thanks for your feedback, however, I would like to clarify this statement for clarity

I wonder if it would be helpful to indicate that a resource is a draft more explicitly than just showing the publish button? The other place we show draft resources is they're explicitly on the drafts page (and remember admins would stop seeing drafts here with issue #11, but non-admins would start seeing drafts with issue #15).

So, is my picked up issue #12 intended to cover issue #11 while leaving room for the implementation of issue #15 or should it be treated as a standalone issue leaving room for both issues #11 and #15 to be addressed?

[textbook]

Specifically within this story as proposed, per the pictures I shared above: it's implicit to the admin users that some of the resources they're seeing are drafts, because they have a publish button. So I wonder, right now, if that should be made explicit or whether we can rely on them to figure it out (or immediately publish their own resources so never see drafts here, or simply not care, etc.). I mention the other two stories because we should always think about our work in context, to help make the best decisions - if we delivered #11 (so admins don't see drafts) but never #15 (so non-admins don't see them either) then we'd never see drafts in this view at all, for example.

[Emmanuel-Dominic]

Hello @textbook, thank you for providing this insight

💡 As I see it, it makes sense, since I buy the idea of returning the user data with the loadingMore option, while displaying only the most recent resources without passing the pagination parameter to the URL.

• Let me work on that shortly.

[textbook]

No problem! If you'd like to work on this further that's great, it's all good practice, but for the Tech Products interview process just focus on getting the pipeline to ✅