superteamdao / earn Goto Github PK

Expected Behavior

Usernames suggested during account creation should be easy to remember while maintaining uniqueness. Ideally, a username should be a concatenation of the user's name and a short sequence of numbers to ensure uniqueness without making it cumbersome.

Actual Behavior

The current username generation algorithm/approach suggests usernames with long strings of numbers appended, such as "dholanipratik973551". This makes the username difficult to remember and unnecessarily long, potentially impacting user experience.

This issue is a paid bounty live on Superteam Earn right now, with a prize pool of $75 USDC. Check it out here.

Expected Behavior

Sponsors should be able to edit their profile details from the sponsor dashboard. To make that happen, the sponsor dashboard needs the following:

1. An edit icon next to the Sponsor name on the dashboard
   If the sponsor name is too big and could break the UI, truncate the name such that the edit icon is visible and not interfering with the vertical light grey line on its right

Actual Behavior

Often the name or PFP of the sponsor needs to be updated which has to be done manually — this helps save time for the sponsor and reduce their dependency on the Earn team.

Two improvements to be made:

• The whole page reloads after liking a submission right now. This is not ideal and should be fixed.
• Improve how the toaster looks visually.

Expected Behavior

Actual Behavior

• FAQs animation on collapse has a weird delay
• Listing Work is overflowing, it rather be scrollable
• Stats are not centered from tablet and below

Expected Behavior

There should be a dark mode so that if we are working at night then our eyes will less strain.

Actual Behavior

There is no option for it in the whole dashboard.

Steps to Reproduce the Problem

1. Go to the dashboard.
2. Search for a Dark theme toggle.

This is very useful feature as many are developers here like me who are always comfortable with dark theme.

Expected Behavior

• Each member row should display a "Remove" button.
• Upon clicking the "Remove" button, a confirmation modal should appear with the following details:
  • Title: "Remove Member?"
  • Subtext: "Are you sure you want to remove <email> from accessing your sponsor dashboard? You can invite them back again later if needed."

Expected Behavior

On clicking the like button the user should be able to like the submission thereby increasing the counter of like by 1

Actual Behavior

Gives error as shown in video above

Expected Behavior

A user should not be able to access the edit page when they are not logged in.

Actual Behavior

By going to url https://earn.superteam.fun/t/<username>/edit/ an edit page is visible to the user even when they are not logged in.
The most important part of the issue is it works for any username
However, the backend logic avoids the changes so there are no worries currently but it still is a bug that needs to be handled.

Screenshots

Steps to Reproduce the Problem

1. Do not be logged in
2. Go to the URL provided above with a username
3. The page will be visible and accessed

By setting up locally, I found the issue and fixed it. It was a minor one :)
would love to raise a PR if you can assign this issue to me !

Cheers !

Expected Behavior

• Liking a submission should be a smooth and quick process without needing to reload the entire page.
• The toaster notification should be aesthetically pleasing and align with our overall UI design standards.

Actual Behavior

• The entire page reloads after a user likes a submission, leading to a disruptive user experience.
• The toaster notification that appears post-liking a submission has an unattractive design, especially concerning its border, detracting from the overall user interface.
  

Steps to Reproduce the Problem

1. Navigate to any submission (earn.superteam.fun/listings/bounties/[slug]/submissions)
2. Click the 'Like' button on the submission.
3. Observe the page reloading and the appearance of the toaster notification.

Ideally use the Toast component from chakra-ui

Adding a Project to Hacktoberfest:

• Add the “hacktoberfest” topic to your repository to opt-in to Hacktoberfest and indicate you’re looking for contributions.

• Apply the “hacktoberfest” label to issues you want contributors to help with in your GitHub or GitLab project.
• Add a CONTRIBUTING.md file with contribution guidelines to your repository.
• Choose issues that have a well-defined scope and are self-contained.
• Adopt a code of conduct to create a greater sense of inclusion and community for contributors.
• Be ready to review pull/merge requests, accepting those that are valid by merging them, leaving an overall approving review, or by adding the “hacktoberfest-accepted” label.
• Reject any spammy requests you receive by labeling them as “spam,” and any other invalid contributions by closing them or labeling them as “invalid.”

More details on the official page

• EUROe
• FIDA token

Actual Behaviour

The podium prize split elements are not middle aligned to the top and bottom borders

When a listing is in draft and has no rewards added, the submissions elements is too close to the border above it

Suggestions for Improvement:

For the Podium Prize Split Alignment: Adjusting the vertical alignment of the podium prize split elements to be centrally positioned within their container could enhance the visual balance and overall aesthetic appeal of the interface.

For the Draft Listing Spacing: Increasing the margin or padding above the submissions element in draft listings could provide a more spacious and less cluttered appearance, potentially improving readability and user experience.

Looking forward to any additional insights or suggestions

Pre-fill the bounty description dialog box with these headings. All of these should be in H1 font:

• About the Bounty & Scope
• Rewards
• Judging Criteria
• Submission Requirements
• Resources

Any user should be able to delete these but should come pre-filled when making a new bounty.

Expected Behavior

Text search should show submission either by matching the name of email in the submissions dashboard.

Actual Behavior

No results are displayed when searching in the submissions dashboard.

Steps to Reproduce the Problem

1. Receive submissions for a bounty.
2. Search for a particular user

This is useful when we have to cross-check that the submissions have signed up, filled another form or signed up for a platform that is being tested and we need to confirm that they actually signed up using email from our end.

Comments under bounties are currently sorted in chronological order i.e. newest is at the top. Change this order to reverse chronological so that newest comments show up at the bottom.

Add a delete option under the three dots to remove a draft.

Note: This option should only be visible for drafts, not for published posts/bounties.

The design as of now looks very out of place:

Match the design of those two cards with the one in the following figma link: https://www.figma.com/file/32RTTrXJb8MQo8bz833ioA?embed_host=oembed&kind=file&node-id=2033-860&type=design&viewer=1

Steps to Reproduce the Problem

1. Create a talent profile
2. Get to the success page

This issue is a paid bounty live on Superteam Earn right now, with a prize pool of $125 USDC. Check it out here.

Expected Behavior

Click on the upload image icon in the listing editor toolbox, and select the image (png or jpeg) to be uploaded to the listing description.

Uploaded images should be compressed before being added to our Cloudinary to save on server costs.

Things to note:

1. Images should always be centre-aligned
2. Resizing the image should be possible but should not break the UI
3. Only jpeg or png formats should be supported
4. Place the upload icon between the Underline and Embed Link icons in the listing editor

Actual Behavior

Users need to upload their images to a third-party website and link the uploaded image to the listing descriptions, leading to suboptimal UX for both talent and sponsors.

Expected Behavior

the toolbar of the editor should be sticky.

Actual Behavior

Right now, it is not sticky which causes the sponsor to scroll back up and down a lot even to change formatting.

Steps to Reproduce the Problem

1. Create a listing
2. Get to the "Description" step of the create listing flow

Once someone has submitted a bounty, a popup needs to be shown to users for feedback about Superteam Earn.

Copy: Help Us Improve Superteam Earn
Text: We'd love to know about your expereince with Earn, and how we can improve!

Clicking on the popup should redirect the user to this form.

• Airdrop 0.001 SOL to everyone who creates a profile
• Add to messaging as well "Create a profile and get enough SOL for 10 transactions on Solana"
• Find the faucet here.

Expected Behavior

• The /src/pages/dashboard/listings/[slug]/submissions.tsx file should be concise, well-organized, and maintainable.
• The file's length should ideally be less than approximately 400 lines to enhance readability and manageability.

Actual Behavior

• Currently, the file is overly long and complex, which hampers readability and maintainability.
• The file exceeds 400 lines, making it challenging to navigate and understand.

Steps to Reproduce the Problem

1. Navigate to the /src/pages/dashboard/listings/[slug]/ directory.
2. Open the submissions.tsx file, and observe the file length and complexity

Proposed Solution

• Refactor the submissions.tsx file to reduce its length and complexity.
• Identify sections that can be modularized into separate components or utility functions.
• Ensure that refactoring does not affect the existing functionality and performance.

Current Behavior

When a new draft is created using a template, the system currently utilizes the template's title as the slug for the listing link. This behaviour can lead to situations where the URL does not accurately reflect the final title given to the listing by the sponsor, potentially causing confusion or misalignment between the listing content and its corresponding URL.

Expected Behaviour

It would be more intuitive and representative if the slug for the listing link were generated based on the actual title provided by the sponsor for the listing, rather than the template title. This change would ensure that the URL is a more accurate reflection of the listing's content, improving clarity and user experience.

Steps to Reproduce the Problem

1. Create a listing using your sponsor profile
2. Select a template, and save the listing as draft

Expected Behavior

Actual Behavior

Results in an error that stops the draft updation

Steps to Reproduce the Problem

1. Create a Sponsor Profile
2. Create a Listing
3. Get to the Rewards Step, and save the listing as a draft listing

Actual Behavior

Expected Behaviour

When discord is not filled (but something else is), we should show a different error.

Steps to Reproduce the Problem

1. Start the talent profile creation process
2. In the socials field, try proceeding without adding the discord link

Expected Behavior

1. When we click outside of the submit form, it should close.
2. It's better to disable the submit button until all the required fields are filled.

Actual Behavior

1. The submit form doesn't close when clicked outside.
2. The submit button is not disabled and is less clickable by default ( We can make its bg-color have less opacity or a faded bg works too).

Steps to Reproduce the Problem

Here is a video to reproduce the problem:

Expected Behavior

When navigating the earn website between different routes I would like for my wallet state to be persisted unless I log out

Actual Behavior

I get disconnected from my wallet

Steps to Reproduce the Problem

1. go to the earn website
2. connect wallet
3. switch between different routes and your wallet connection gets disconnected.

possible fix

use context or a state management library e.g zustand or recoil

"0 characters left" is confusing.

• Show how many characters are being exceeded, i.e. show "-10 characters left"?
• Or simply show "Character limit exceeded. Please reduce the text"
  

Expected Behavior

I am unable to log in via email on my local setup. I would love to contribute by adding signup and login functionalities, as well as incorporating some test users for local setup. Thank you!

Actual Behavior

resend dashboard

Steps to Reproduce the Problem

1. go to homepage
2. click on login
3. login though email

Expected Behavior

• The web-app should render consistently on both the server and the client, ensuring a smooth hydration process without errors.
• The initial UI rendered by the server should match the UI rendered on the client.

Actual Behavior

• The application is experiencing hydration errors, as indicated by the error message: "Error: Hydration failed because the initial UI does not match what was rendered on the server."

Steps to Reproduce the Problem

1. Run the app using pnpm dev
2. Observe the localhost for hydration error messages during page load.

This issue is a paid bounty live on Superteam Earn right now, with a prize pool of $75 USDC. Check it out here.

Expected Behavior

Pre-fill the auto-generated slug whenever a new listing title is added to the listing creation flow. Allow users to edit the slug while checking for duplicates. If the slug already exists show an error message right below the field in red text (same component as used for social link errors, or duplicate sponsor profile names error for example).

Duplicate the Listing Title field component for style, etc. The slug field should be right below the Listing Title field.

Actual Behavior

Right now it’s not possible to do this from the frontend.

Superteam Earn is now fully optimised for mobile. We want to educate and prompt our mobile users to install the Earn PWA.

• Show this modal to Mobile users
  

• The modal should be shown once per user (use localstorage to track this), and should only be shown on mobile. Use user-agents to identify mobile device

• Check out this guide on how to make PWA installable in one click, from the mobile browser. But would advice to do more research on the same, in order to make this work for both iOS and Android devices, as well as both Safari and Chromium browsers.

In browsers which the one-click installation is not possible, show the following modal:

Design Link for both modals

The Problem:

Setting up a database each time is time-consuming and can introduce initial configuration errors. This process involves installing software, configuring settings, and ensuring compatibility, which often leads to inefficiencies and potential issues.

Solution:

Utilizing Docker simplifies the process by allowing users to effortlessly spin up the database according to predefined configurations, eliminating the need for repetitive setup tasks.

Expected Behavior

yarn dev command should run the project smoothly across all platforms(mac, linux and windows). And other similar commands.

Actual Behavior

yarn dev does not run the project in windows and throws error. The command in package.json does not follow windows syntax and it needs to be updated to Set NODE_ENV=development & next dev to run the project.

Steps to Reproduce the Problem

1. Clone the project on a windows system
2. Run yarn install followed by yarn dev and check logs.

Solution

By adding cross-env package to the project and replacing existing commands with cross-env commands prefix is the easiest way to do this.

https://www.loom.com/share/509324ec5bc944809e4223f0995450b4?sid=07bdb726-6700-4536-801b-8b624eb5a42f

Hello maintainers,

I noticed that the README.md and CONTRIBUTING.md files are missing a crucial step regarding Prisma migration and client generation. This step is essential for contributors to properly set up the project environment and contribute effectively.

I have made the necessary changes to include instructions for Prisma migration and client generation in both files. These changes will help streamline the onboarding process for new contributors and ensure that everyone can easily get started with the project.

I kindly request you to review my changes and consider merging them into the main branch. If there are any further adjustments or clarifications needed, please let me know, and I'll be happy to address them.

Thank you for your attention to this matter.

Best regards,
Sumit Kumar

expected behavior

actual behavior

Expected Behavior

Updated logo of the Twitter

Actual Behavior

The old blue bird logo of Twitter

Steps to Reproduce the Problem

1. Go to https://earn.superteam.fun
2. Scroll till the bottom of the page
3. Notice the old Twitter logo in the footer section

Pls assign this issue to e so that I can work on a fix for this issue @a20hek

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

OG images for references are not cropping properly

Steps to Reproduce the Problem

1. Create a project listing
2. Add reference links in the creation process
3. Publish the listing, and check the references tab of the listing

use browser local storage of indexed db to save a form when a user fill it and does not submit it so that he can maybe continue later.

As we increase the number of tokens supported, it will make it much harder to scroll and find the right token. Hence, search is better

This component can be found here

Description:

The project's README.md and CONTRIBUTING.md lack detailed local setup instructions, which can hinder new contributors.

Solution:

Add a step-by-step guide covering cloning, dependency installation, environment variable setup, and running the development server. This will ease onboarding and reduce entry barriers.

I would like to work on this issue if it is considered valid

Expected Behavior

The web page should not automatically refresh itself

Actual Behavior

The webapp keeps refreshing itself when applying for a bounty, resulting in resetting the form I have filled.

Steps to Reproduce the Problem

1. Go to the earn website
2. Find and project and try to fill in the details and wait for a short while. The web page will refresh itself resulting in loss of all details you had filled.

ENVIRONMENT

Broswer: Brave Browser 123.1.64.113
OS: Pop OS

Expected Behavior

In this bounty, the UI shouldn't ideally break.

Actual Behavior

It's breaking

Probably it's due to some max-width/max-height limit not being adjusted in the description.

Expected Behavior

the calendar in the create listing form should open up when clicked anywhere on the bounding box

Actual Behavior

It opens only after the icon is clicked on.

Suggestions about the UX Improvements:

1. Calendar should pop when anything is clicked
2. Provide small pills of "1 week, two week" etc to add deadline with just one click

Expected Behavior

Hovering on each stat should give more information about the same, similar to the following:

Actual Behavior

Steps to Reproduce the Problem

1. Create a sponsor profile
2. route to /dashboard/listings