You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue
The process of officially submitting a Job Post through the UI is not descriptive enough.
Suggestion
Make the state changes along the way descriptive. when a user clicks submit, he should be made aware of what is going on. When a job I submitted, he should be immediately taken to the Job posts page and see a placeholder for the submitted job that shows a pending status until the transaction has been confirmed on chain
The text was updated successfully, but these errors were encountered:
because in order to this. we need to maintain two arrays
pending projects
on-chain projects
but the problem is. 1) pending projects have no project id yet.
when we join two arrays, there should be a common key(like a foreign key in DB) to compare.
as 1) doesn't have any project id so there is no way to do it.
sure, title/ tokenURI ... can be one of the candidates. but not always identical.
estimating project id via "contract.getLatest() + 1" would be good option. but still, there is a chance to be a race condition when other clients create a project at the same time.
we can do this when there is a unique project id that can be decided before going to on-chain.
Work Page / Job Submission
Issue
The process of officially submitting a Job Post through the UI is not descriptive enough.
Suggestion
Make the state changes along the way descriptive. when a user clicks submit, he should be made aware of what is going on. When a job I submitted, he should be immediately taken to the Job posts page and see a placeholder for the submitted job that shows a pending status until the transaction has been confirmed on chain
The text was updated successfully, but these errors were encountered: