Adding more details to the Unsplash Collection task #17
cezary-klauza
started this conversation in
Feature request
Replies: 1 comment
|
So far, the challenges have been quite open, and up to how you want to implement. But I am working on making the description better. I'll update the description to give developers more direction in the near future. Thank you for your suggestions, I'll definitely consider it and add it to the challenge. 🙏 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In the task description, the only useful piece of information about creating the entire application is the link to the API documentation.
Creating the application itself isn't a problem until it comes to handling collections.
It's not specified how collections should work. Should they be stored in local storage, cookies, or should Unsplash authorization be used with a bearer token? Even once the developer chooses one of these options, there are still additional questions, for example:
Using Unsplash authorization:
I personally chose the option with Unsplash authorization, and I think it would be helpful to change the design of the navbar to allow users to log in via Unsplash and log out of the session.
Additionally, there should be an option to create, delete, and modify collections, as it's pointless to add photos to collections that we have to create directly on the Unsplash site.
I was thinking about implementing the authorization in a way that's convenient for the user, which would be:
It would be great if you could analyze the issues I mentioned earlier and clarify for future developers how they should approach this task :D
All reactions