Giter Club home page Giter Club logo

valorant-checker's Introduction

LinkedIn Badge

Hello there!

👨‍💻 About Me :

Hello! My name is Joseph and I am a software engineer in Southern California.

I'd love to contribute to any projects and applications that have a positive impact on the community.

Before entering the tech industry, I worked in the healthcare field for several years. Over this time, I gained a strong work ethic, with great admiration for the strong teamwork, coordination, and problem-solving that it entailed. I was introduced to the software development world by friends who suggested it due to its similarities to the medical field in the ways that I loved it.

After months of soul-searching, self-studying, and research into the field, I decided to delve into it further and immerse myself in a boot camp program, and I have continued loving it since!

I'm excited to keep moving forward in this industry, solving problems with a like-minded group of teammates, and continuing this path of ongoing growth!

I’d love to connect!

  • 🔭 Build frontend, backend, and full-stack web applications.

  • 🌱 Always striving to learn more.

  • ⚡ Practice with new technologies when I can.

  • 📫How to reach me: Linkedin Badge

TypeScript  React  Next HTML  CSS  JavaScript Vue   VS Code   NodeJS   PostgreSQL   Webpack   Firebase   Babel   Git   Tailwind   Photoshop   Figma  

🔥 My Stats :

GitHub Streak

Top Langs

valorant-checker's People

Contributors

joseph-w-valdez avatar

Watchers

avatar

valorant-checker's Issues

Feature: User can view details about each ability

⚙️ Feature

What capability will users have when this feature is merged?

User can view details about each ability.

📐 Functionality

A description of how the application will work from the perspective of the user.

When the user is on the Individual Agent page view, they may click on any of their listed abilities to switch to the Individual Ability page view, which will populate relevant details about that ability.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

image

image

image

✅ Task List

Commit checklist for tasks needed to complete the feature.

  • Add cursor:pointer to the ability containers

  • Add event listeners to the ability containers

  • Create new page view for individual ability

  • Create handler function to swap to the individual ability page view and use the API to fill in the corresponding information

  • Modify responsiveness so portrait shows up with wider viewport widths

  • Create back buttons with handlers to go back to the previous page view, which should be either individual agent or 'agents' page currently

  • Clean Up

    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can view specific weapon details

⚙️ Feature

What capability will users have when this feature is merged?

User can view specific weapon details.

📐 Functionality

A description of how the application will work from the perspective of the user.

When the user is on the Weapons page view, they can select a weapon which will swap them to the Individual Weapons page view to display correlated details about that weapon.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

image

image

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Create new page view for individual weapons with proper styling
  • Ensure that page view function works with new page view
  • Add new render function to add table in a similar manner to previous page views but for weapon stats
  • Add event listeners to the tr elements of weapons in the weapons page view
  • Look through populated stats and removed unecessary ones, such as shotgun pellet count for non-shotgun weapons
  • See if any data needs to be converted to be easily readable for the user
  • Add a back button to go back to the weapons page view
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can filter playable characters by role

⚙️ Feature

What capability will users have when this feature is merged?

User can filter playable characters by role

📐 Functionality

A description of how the application will work from the perspective of the user.

When the user is on the Agent page view, they may click the radio buttons corresponding to different Agent roles. This will generate a new list of playable characters that belong to that role.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

Joseph_Valdez_AJAX_Project1024_2

Joseph_Valdez_AJAX_Project1024_3

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Add in filter table with functionality
  • Make it so that only one button can be clicked at a time
  • Allow clicking on the icon (if present) and label to also check the box
  • Modify the DOM creation code to only add in characters that meet that role criteria
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can view all playable characters

⚙️ Feature

What capability will users have when this feature is merged?

User can view all playable characters

📐 Functionality

A description of how the application will work from the perspective of the user.

The user will be able to click on the Agents button on the navbar to be directed to the Agents page view which will populate a list of playable heroes based off of the items received from the Valorant API.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

Joseph_Valdez_AJAX_Project1024_1

Joseph_Valdez_AJAX_Project1024_2

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Create the Homepage page view with proper styling
  • Create the Agents page view with proper styling and give it the class hidden by default
  • Add proper CSS pseudoselector rulesets to make sure that the buttons are clickable and have the pointer cursor when hovered over.
  • Create proper view swapping code to switch between these page views.
  • Create click event listeners for the navbar items to use the view swapping code properly
  • Connect the page to the Valorant API
  • Create a list of items consisting of the Agent's names and their killfeed icons pulled from the Valorant API
  • Style the rows so that they alternate in background color and font color
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can view all usable weapons

⚙️ Feature

What capability will users have when this feature is merged?

User can view all usable weapons.

📐 Functionality

A description of how the application will work from the perspective of the user.

The user can click

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

image

image

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Create new Navbar item Weapons
  • Create new page view for weapons with proper styling
  • Modify API function to take weapons as a parameter and append a proper list of all weapons in the game with proper styling from previous issue in the agents view
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can filter usable weapons by type

⚙️ Feature

What capability will users have when this feature is merged?

User can filter usable weapons by type.

📐 Functionality

A description of how the application will work from the perspective of the user.

When the user is on the Weapons page view, they can click on the filter radio buttons to repopulate the list with weapons matching that type.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

image

image

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Add in filter table with functionality
  • Make it so that only one button can be clicked at a time
  • Modify the DOM creation code to only add in characters that meet that role criteria
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Feature: User can view character abilities and biographies

⚙️ Feature

What capability will users have when this feature is merged?

User can view character abilities and biographies

📐 Functionality

A description of how the application will work from the perspective of the user.

When the user is on the Agent page view, they may select an agent to bring up the Individual Agent page view, which will fill the page with corresponding data, showing their biography and list of abilities.

🖼️ Wireframes

Wireframe screenshot(s) of what the app should look like when it is complete.

Joseph_Valdez_AJAX_Project1024_3

Joseph_Valdez_AJAX_Project1024_4

✅ Task List

Commit checklist for tasks needed to complete the feature.
  • Create event listener for the tbody targeting the tr
  • Amend the DOM render function so that it applies an Id value corresponding to that agent's name
  • Create individual agent view in the HTML with proper styling and responsiveness
  • Add an event listener to use the viewswap function to go to the individual agent view
  • Modify the API function to populate the page with corresponding data
  • Create exception to the Passive ability so that it hides that element if no corresponding ability was found
  • Clean Up
    • Remove all buttons and placeholders that do not serve the functionality of the feature.
    • Remove all console logs.
    • Remove all commented out code.
    • Remove all CSS properties that have no effect.
    • Check all code for proper formatting and indentation.
    • Confirm that there are no errors in the console while using the application.
    • Confirm that all previous functionality still works without errors.
    • Confirm that the user interface looks natural on both mobile and desktop screens.
    • Create GIFs of the feature being used on both mobile and desktop screen sizes for inclusion in Pull Request.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.