#50 Landingpage modification
Closed by lbrabec. Opened by emma50.
fedora-qa/ emma50/landingpage landingpage_modification  into  master

Download 50.patch

Issue

https://pagure.io/fedora-qa/landingpage/issue/49

Changes

  • Remove redundant code from every file in the landing-page folder
  • Created a functional component with the name final-stat and beta-stat to hold the stat table
  • Converted blocker component from a class component to a functional component because the state in constructor function is redundant

2 new commits added

  • Merge branch 'landingpage_modification' of ssh://pagure.io/forks/emma50/fedora-qa/landingpage into landingpage_modification
  • Landingpage modification

1 new commit added

  • Refractor code and add @reduxtoolkit

Changes

  • Made use of redux toolkit for efficient redux development.
  • Removed error and warning messages on the browser console by up updating
    dependencies and refactoring code.
  • Created a spinner for wizard route

Less I forget I also change every class component in the project to a functional component, which gives each component the ability to access react hooks.
React hooks is 100% the future of react. This will make the project future-proof.

2 new commits added

  • Merge branch 'landingpage_modification' of ssh://pagure.io/forks/emma50/fedora-qa/landingpage into landingpage_modification
  • Refractor code and add @reduxtoolkit

1 new commit added

  • Add bundle size analyzer and code splitting

Whenever we want to improve the loading performance of a web application it's important to know it's bundle size and eliminate unneeded import so unnecessary code does not get bundled with the app.

Changes

  • Analyze bundle size with the source-map-explorer tool
  • Code-splitting/lazy-loading to split bundle into multiple pieces to load only what is necessary
    for a given route.
  • Removed lodashjs and replace it with ramdajs which has a smaller bundle size and is
    designed for functional programming style
  • Replaced lodash and made use of nanoid to generate unique id

Thanks for participating in contribution period of Outreachy. This pull-request has not been selected to be merged and will be closed for housecleaning purposes. We may revisit this pull-request later, but as of now we will focus on merging pull-requests from our accepted intern.

Pull-Request has been closed by lbrabec

Metadata