armitage-labs / armitage-monorepo Goto Github PK

Create and configure new WalletConnect keys that provide access to the Base chain.

Note that with the support of Base, we also need to refactor and modify the code that creates new Private attestations, as they currently only support Ethereum Sepolia;
This likely includes:

• Making sure that the provider for Base can be selected by the user when creating a new private attestation;
• Making sure that the frontend client can understand which chain the user has selected, and choose the correct schemaID of that chain (look for private data schema ID) -> currently we only have the Sepolia one hardcoded.

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

• Do you want to request a feature or report a bug?
  bug

• What is the current behavior?
  Open attestation in EAS opens on the same tab

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  Click on attestation button on a repository calculated
  Generate public attestation
  click on View in EAS

• What is the expected behavior?
  Open on a new tab

• What is the motivation / use case for changing the behavior?
  UX

If you have recently ran the app locally, and is trying to contribute to the project, we would love to hear from you.

Please use this issue to discuss documentation updates, or to talk about any hurdles you had while setting the project locally.

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

• What is the current behavior?
  When a TX fails, the loading does not stop

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  Create an attestation, then try to create another attestation with the same calculation scores, it should fail due to it being exactly the same.

• What is the expected behavior?
  Loading modal shows that the transaction failed and does not keep loading forever

• What is the motivation / use case for changing the behavior?
  UX

On the /teams/contributors/[contributorId] we need to display the contributorScore intervals as a timeseries chart as part of the data that we display of a user that is part of a team.

This data already exists on the database, and lives under UserScore.score_interval as an array of numbers.

We simply need to parse this data, and construct the graph.

We should have a component on the teams/new/page.tsx that display on the 2nd step of the team creation, together with the table that fetches the github repositories, a box/card/dialog that allows the user to input an arbitrary open source repo to include in his team.
This repository should be added into the team in the same way as any selected one.

Note: Private repositories are not allowed on this scope, and they should be only selected by the table
Note: Creating a component to display the repositories already selected is not part of the scope of this ticket, but a nice-to-have

The following mockup is a simple suggestion and idea on how that could look like during the creation of a team

Some users are complaining about the white theme on the dashboard. We need to help their eyes to be safe 😄

We already have all dependencies installed, and the toggle to do the theme switch on the header.

See src/components/theme/theme-toggle.tsx

It simply needs to be properly configured with NextJs and shadcn/ui.

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

• Do you want to request a feature or report a bug?
  Bug

• What is the current behavior?
  After creating a public or private attestation, the modal that opens on the attestation button keeps the previous state

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  Create new attestation
  Close modal
  Open attestation modal again through button

• What is the expected behavior?
  Modal should allow user to create a new attestation

• What is the motivation / use case for changing the behavior?
  Allow users to create new attestations without refreshing the page

We need to enable functionality from the frontend, specifically on a team view, that allows a user to create a new public attestation of contributor scores.

Initial idea is to create different options when the user clicks the "private attestation" button. Therefore refactoring it to only "attestations"

Upon the modal appearance, the user should need to select between two buttons on the modal, to select either a private attestation or public attestation flow, that will then prompt the transaction on the user wallet and enable him to create the attestation

Through early feedback with users, we discovered that the concept of Teams are more fluid than we initially thought.

Therefore we need to enable a user to be able to remove and add github repositories to a team object.

This should be done on the Github Repositories component of a team details page:

Adding and removing a github repository should automatically update the Team object on the database, and upon save, it should create a new calculation request.

On the settings page, we need functionality for the user to register a specific wallet as his main account wallet.
He doesn't necessarily needs to connect with this specific wallet to create attestations or to interact with the app, but it will be needed for DAO/Token creation.

As part of this functionality, the user will be prompted to sign-in-with-ethereum (SIWE) and sign a message to prove he controls the private key of this wallet.

This functionality should also show which wallet is registered to that user account, in case one has already been added

We need to filter to ensure that we don't let users register repos with size <= 0

Total team CRED: Need to be updated to say +% compared to last week, or something like that

Team CRED earned this week: Is not showing the - sign correctly

We should create a new schema for onchain attestations of contributor scores.

This is necessary for integrations with new chains and other applications;
The schemaIDs of these new schemas should be saved on the application configuration and mapped to which specific chains they point to;

Feel free to create this configuration as a .env variable, a json or yaml file.

e.g.:
attestationPublicSchemaIds: base: 0x2137839 sepolia: 0x12384 optimism: 0x1234 etc...

These schemas should follow the following structure:

githubUsername;
measuredAt;
weightsConfig;
repositoryName;
organizationName;
userScores

We need a function that we can call from the frontend to create a public attestation for a user.

This function needs to be able to use the correct schemaID depending on the chain the user is connected to, receive the data of a contributor score and mint the attestation using the user provider

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

• Do you want to request a feature or report a bug?
  bug

• What is the current behavior?
  Attestation breadcrumb routes to /dashboard/attestations instead of /dashboard/attestation

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  Click on your profile picture
  Go to attestations
  Click on an attestation
  Click on the breadcrumb for navigation

• What is the expected behavior?
  go to /attestation

• What is the motivation / use case for changing the behavior?
  Bug

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.
    

• Do you want to request a feature or report a bug?
  Bug

• What is the current behavior?
  Comments are not ranked properly

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  See any contributor details

• What is the expected behavior?
  Ranks to be assigned correctly based on the nominal value of comments

• What is the motivation / use case for changing the behavior?
  Comments are ranked wrongly

Whenever a user is on the team details page, a button should be displayed to create an attestation (prob using https://attest.sh/) about all contributors and their contributions scores. This attestation for now should not be displayed on the page and the UX is out of scope for this issue.

We should probably create a new DB model to save those attestations, happy to discuss other ideas and scenarios to tackle that.

Feel free to discuss on this ticket how the UX could look like and propose ideas

Currently the application is not able to verify if the user has already installed the GithubApp on his profile or organization.

Therefore, the banner on the overview dashboard does not disappear after the user has changed its settings.

This issue should create logic that verifies such installation, and removes the component from the overview dashboard if the user has successfully installed the app to allow private repositories.

We need to export user contributions from a team or repository on a CSV format.

Initial idea is to generate and export a CSV from the user table that is displayed on both repositories and teams.

Currently, the feedback/help link sits on the page bar of the dashboard.

That's not it's place 😃

We need to create a floating balloon-like component that will be displayed on the bottom right or left corner of the screen, to allow easy access to the user for feedback