publiclab/mapknitter

Planning Issue: Upgrade rails from 3.2 to rails 6

Open

#305 opened on Jan 26, 2019

View on GitHubContributor guide
 (32 comments) (0 reactions) (4 assignees)Ruby (203 forks)auto 404
discussionenhancementhelp wantedplanning

Repository metrics

Stars
 (274 stars)
PR merge metrics
 (PR metrics pending)

Description

  • Rails upgrade
  • Rails 3.2 => Rails 4.0
  • Rails 4.0 => Rails 4.1
  • Rails 4.1 => Rails 4.2
  • Rails 4.2 => Rails 5.0
  • Rails 5.0 => Rails 5.1
  • Rails 5.1 => Rails 5.2
  • Rails 5.2 => Rails 6.0
  • UI update and collaborate with others
  • Fix existing deprecation warnings
  • Write Test Coverage for new Rails 6.0 Unit testing Functional testing
  • JS API endpoints of MapKnitter
  • write Functional Test
  • Karma, Jasmine, Mocha, QUnit. Decide which one??
  • Code Clean up after upgrade to Rails 6.0
  • Generate Code Coverage Report
  • Add git tools
  • codeclimate
  • codacy
  • codecov Part of #300

Contributor guide

Research direction
Identify the remaining unchecked tasks from the checklist and determine the current state of the Rails upgrade. Focus on tasks marked as unchecked, such as JS API endpoints, functional tests, and code cleanup. Review the project's contribution guidelines and check for any existing work on these tasks.
Tech stack
rubyjavascript
Domain
backend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RubyRuby on RailsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20