Skip to content

Conversation

@Sepulator
Copy link
Owner

@Sepulator Sepulator commented Sep 21, 2025

  1. Task: REST Client
  2. Screenshot:
  3. Deployment: netlify.app
  4. Done 21.09.2025 / deadline 30.09.2025
  5. Youtube video
  6. Score: 490 / 500

Main route - max 50 points

  • The Main page should contain general information about the developers, project, and course. - 10 points
  • In the upper right corner there are 2 buttons: Sign In and Sign Up. - 10 points
  • If the user is authorized, there should be a Main Page button instead of Sign In and Sign Up buttons in the upper right corner. - 10 points
  • If the token is expired/invalid - the user should be redirected from the private routes to the Main page (it might happen either automatically, on page refresh or on route change). - 10 points
  • Pressing the Sign In / Sign up button redirects a user to the route with the Sign In / Sign up form. - 10 points

Sign In / Sign Up - max 50 points

  • Buttons for Sign In / Sign Up / Sign Out are everywhere where they should be. - 10 points
  • Client-side validation is implemented. - 20 points
  • Upon successful login, the user is redirected to the Main page. - 10 points
  • If the user is already logged in and tries to reach these routes, they should be redirected to the Main page. - 10 points

RESTful client - max 150 points

  • Functional editor enabling query editing and prettifying, request body provided in the URL as base64-encoded on request submit. - 35 points
  • Functional read-only response section, with information about HTTP status and the code. - 30 points
  • Method selector, shows all the valid HTTP verbs, value is provided in the URL on request submit. - 15 points
  • Input for the URL, entered value is provided in base64-encoded way on request submit. - 20 points
  • Headers section, value is provided in the URL on request submit. - 20 points
  • Code generation section. - 30 points

History and analytics route - max 100 points

  • History and analytics is server-side generated and shows informational message with links to the clients when there are no requests in the database. - 20 points
  • User can navigate to the previously executed HTTP request to the RESTful client, HTTP method, URL, body, headers are restored. - 30 points
  • The following analytics are recorded to the database from the application server side and displayed to the user: request duration, response status code, request timestamp, request method, request size, response size, error details, endpoint/URL. - 50 points

Variables route - max 50 points

  • Variables show all the added variables, restores them from the local storage on load. - 15 points
  • User can add new, or delete an existing variable, variables in the local storage are updated on change. - 15 points
  • Variables are used in the request before the request execution. - 20 points

General requirements - max 50 points

  • Multiple (at lest 2) languages support / i18n. - 30 points
  • Sticky header. - 10 points
  • Errors are displayed in the user friendly format. - 10 points

Youtube video - max 50 points

IlinJoy and others added 30 commits September 3, 2025 11:10
…into feat/add-base-routing-folder-structure
…provement

Chore/pr template and linting improvement
…into feat/add-base-routing-folder-structure
Sepulator and others added 30 commits September 21, 2025 20:05
fix: handle proper authentication
fix: revert clearing response on initialize
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.

4 participants