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

HUM-99: available jobs service refactor #3032

Conversation

adrian-oleskiewicz
Copy link
Contributor

@adrian-oleskiewicz adrian-oleskiewicz commented Jan 21, 2025

Issue tracking

HUM-99

Context behind the change

Split file into hooks, schema, types

How has this been tested?

  • checked if available jobs are correctly displayed
  • checked if user is able to select a task

Release plan

normal deploy

Potential risks; What to monitor; Rollback plan

N/A

Copy link

vercel bot commented Jan 21, 2025

Someone is attempting to deploy a commit to the HUMAN Protocol Team on Vercel.

A member of the Team first needs to authorize it.

@adrian-oleskiewicz adrian-oleskiewicz marked this pull request as ready for review February 10, 2025 11:33
@adrian-oleskiewicz
Copy link
Contributor Author

@dnechay ready for review

@dnechay dnechay self-requested a review February 10, 2025 12:55
Copy link
Contributor

@dnechay dnechay left a comment

Choose a reason for hiding this comment

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

New "fetch-available-jobs" service is really a "service" now, because it has no react-specific logic, just API-related stuff.

However, I don't think it makes sense to split it to service, schema and types file, it all can live in a single file. Later if we come up to some kind of jobService (that will hold all job-related API calls) - it can make sense, but right now we just producing more & more "nano" files that doesn't make a lot of sense. So let's keep things together for now

@mpblocky mpblocky force-pushed the HUM-99-available-jobs-data-refactor branch from 5fdc61a to 8602c56 Compare February 25, 2025 10:10
@mpblocky
Copy link
Contributor

@dnechay this one is ready as well. I think further changes should be commited here as adding more here could cause unnecessary conflicts

@dnechay dnechay self-requested a review February 25, 2025 10:44
Copy link
Contributor

@dnechay dnechay left a comment

Choose a reason for hiding this comment

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

LGTM overall

One question: do we need to export availableJobSchema and availableJobsSuccessResponseSchema, @mpblocky ? They don't seem to be used anywhere else

@mpblocky
Copy link
Contributor

@dnechay You are right, it was exported before and forgot about it while removing it's duplicates. Fixed!

Copy link

vercel bot commented Feb 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
human-app ❌ Failed (Inspect) Feb 26, 2025 9:58am

@mpblocky
Copy link
Contributor

mpblocky commented Mar 3, 2025

@dnechay can You merge this PR? It blocks me a bit from further work

@dnechay dnechay merged commit d7e9a3a into humanprotocol:develop Mar 3, 2025
4 of 9 checks passed
@dnechay dnechay mentioned this pull request Mar 3, 2025
26 tasks
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.

3 participants