Skip to content
YLcoding edited this page Jun 12, 2020 · 31 revisions

Codacy Badge Maintainability ESLint Test Coverage checker e2e Tests Unit Tests Release and Publish

Welcome to CartoGraphX!

What is CartoGraphX?

CartoGraphX is a combination of a VS Code extension and a web application that provides software development teams with a way to visualize their coding projects! Our software utilizes the files in a project in order to create a map that helps developers understand the relationships between the files they are working in much like the one displayed below:

CartoGraphX keeps track of where team members are working and updates automatically to reflect changes made to files in VS Code

Give CartoGraphX a try!

Go to the VSCode Marketplace, and search CartoGraphX. click on the install, and reload your VSCode. Once installed, You should get a notification that CartoGraphX is now active! Click on the CGphX command on the toolbar to get started.

Features: To view the extension commands, press the CGphX button on your status bar (bottom bar). This will prompt a dropdown menu in VSCode providing you with the available commands.

If you are an existing user, you can sign in. If you are a new user, sign up with valid credentials and you are good to go.

Once signed in, navigate to a git repository of your choice, and click on the CGphX command to access all of the commands.

When signed in, you have the ability to do a variety of features. To access those features, hit the CGphX button. The features and their descriptions are found below:

1. Display Current Working File: A popup window with your current file and the lines of code will appear.

2. Get User Info: Gets the account email that you are currently signed in to.

3. Sign Out: This command will allow for the person to sign out of their CartoGraphX account.

4. Create Map: Will create a map of the git repository you are currently in and open it in the VSCode window. It will give you a key which you can load now and save for later.

5. Load Map: Will load a map key of your choice into the VSCode window.

Want to help? Prepare yourself to be a part of the team!

How do you feel after using CartoGraphX? Maybe you like it a lot! You might also think there is still a lot of room for improvement. If you see the potential of our project idea and willing to help to improve the product, we are more than welcome!

In order to prepare yourself before writing your first line of code for CartoGraphX, or even look into the code, it's important that we are all onboard on the design decisions and visions we had on CartoGraphX.

Here is a list of project artifacts that will help you understand these visions!

Write your first line of CartoGraphX code!

After getting a firm understanding of our product visions, it's time to write your first line of CartoGraphX code! yay! However, contributing to an open-source project codebase will never be easy, especially if you have no experience in VS Code Extension development. It's important to understand what is in each file and how they work to gather to make up the features we have so far.

But no worries, we got you covered! We have carefully thought about how to bring a new developer onboard. Following is a helpful process you want to follow:

  1. Check out the Codebase Tour to understand the structure of our codebase!
  2. Use Developer Onboarding to understand how to set up the dev environment before writing the code.
  3. When you writing the code, make sure to follow the Style Guidelines and comment your code using Comment Guidelines!
  4. Fork the CartoGraph repo using our Git Guidelines and make your changes there!
  5. TEST is very important! Write your test for your code ALWAYS using these two guidelines (Write Unit Tests and Write E2E Tests).
  6. When you tested your code and ready to merge your code to master, please follow the Create a Pull Request guidelines for your pull request!
  7. Review your code and review other people's code will help everyone! Using our Code Review Guideline to do code review for the pull request!

Improve our build process

We have Github Actions CI/CD pipelines that are running 24/7 to protect the integrity of codebase and make sure all the features of our app are always working. Just like the codebase, the pipeline also could use some help for improvement.

To understand how our build pipelines work, please read following document:

Feedback and Suggestion

Join our Slack channel to reach out to us for any feedback and suggestion!

Clone this wiki locally