refactoring

1. Daftar Project

https://github.com/aufawibowo/semeru-api

2. Hasil Refactoring

refactoring
1. Daftar Project
2. Hasil Refactoring

2.1 Aktivitas Refactoring: Implementing SRP

Kategori: SOLID
Permasalahan: Spaghetti Code didalam satu controller, dimana semua implementasi input/output handlers, implementasi bisnis, dan database query berada di dalam satu fungsi.
Solusi: Untuk handlers, dipecah menjadi kelas request dan service sendiri\

Potongan code sebelum refactoring

/*
https://github.com/aufawibowo/semeru-api/blob/2.9/app/Http/Controllers/RtpoControllerNew.php 1162
*/
public function approve_reschedule_sik(Request $request)
{
	date_default_timezone_set("Asia/Jakarta");
	$date_now = date('Y-m-d H:i:s');
	$periode = date('Y-m');

	$sik_no = $request->input('sik_no');
	$username = $request->input('username');
	$reason = $request->input('reason');
	$is_approved = $request->input('is_approved');
	//$username = 'enggarrio';
	settype($is_approved, "boolean");
	$rtpo_users_data = DB::table('users')
	->select('*')
	->where('username',$username)
	->first();

	$rtpo_nik = $rtpo_users_data->id;
	$rtpo_cn = $rtpo_users_data->name;

	if($is_approved){
	$approve = DB::table('propose_reschedule')
	->where('sik_no',$sik_no)
	->update([
		'status' => 1,
		'status_desc' => 'WAITING FOR NOS APPROVAL',
		'rtpo_nik' => $rtpo_nik,
		'rtpo_cn' => $rtpo_cn,
		'last_updated' => $date_now,
		'is_sync' => 0,
	]);

	$res['success'] = 'OK';
	$res['message'] = 'Success';
	
	return response($res); 
	}
	else{
	$approve = DB::table('propose_reschedule')
	->where('sik_no',$sik_no)
	->update([
		'status' => 2,
		'status_desc' => 'REJECTED BY RTPO',
		'reject_reason' => $reason,
		'rtpo_nik' => $rtpo_nik,
		'rtpo_cn' => $rtpo_cn,
		'last_updated' => $date_now,
		'is_sync' => 0,
		]);

	$res['success'] = 'OK';
	$res['message'] = 'Success';
	
	return response($res); 
	}
}

Potongan code setelah refactoring

// Request.php
<?php


namespace Semeru\Rtpo\Core\Application\Services\ApproveRescheduleSIK;


class Request
{
    public ?string $sik_no;
    public ?string $username;
    public ?string $reason;
    public ?string $is_approved;

    /**
     * Request constructor.
     * @param string|null $sik_no
     * @param string|null $username
     * @param string|null $reason
     * @param string|null $is_approved
     */
    public function __construct(?string $sik_no, ?string $username, ?string $reason, ?string $is_approved)
    {
        $this->sik_no = $sik_no;
        $this->username = $username;
        $this->reason = $reason;
        $this->is_approved = $is_approved;
    }

    public function validate()
    {
        $errors = [];

        if (!isset($this->sik_no)) {
            $errors[] = 'sik no must be specified';
        }

        if (!isset($this->username)) {
            $errors[] = 'username must be specified';
        }

        if (!isset($this->reason)) {
            $errors[] = 'reason must be specified';
        }

        if (!isset($this->is_approved)) {
            $errors[] = 'is approved must be specified';
        }

        return $errors;
    }
}

// Service.php
<?php


namespace Semeru\Rtpo\Core\Application\Services\ApproveRescheduleSIK;


use Semeru\Rtpo\Core\Domain\Exceptions\ValidationException;
use Semeru\Rtpo\Core\Domain\Models\Rtpo;
use Semeru\Rtpo\Core\Domain\Models\SikNo;
use Semeru\Rtpo\Core\Domain\Repositories\RtpoRepository;
use Semeru\Rtpo\Core\Domain\Repositories\SikRepository;

class Service
{
    private SikRepository $sikRepository;
    private RtpoRepository $rtpoRepository;

    /**
     * Service constructor.
     * @param SikRepository $sikRepository
     * @param RtpoRepository $rtpoRepository
     */
    public function __construct(SikRepository $sikRepository, RtpoRepository $rtpoRepository)
    {
        $this->sikRepository = $sikRepository;
        $this->rtpoRepository = $rtpoRepository;
    }

    public function execute(Request $request)
    {
        $errors = $request->validate();

        if (count($errors) > 0) {
            throw new ValidationException($errors);
        }

        $rtpo = new Rtpo(
            $this->rtpoRepository->getRtpoId(),
            $this->rtpoRepository->getRtpoUserData(),
            new SikNo($request->sik_no),
            new \DateTime('now')
        );

        $waitingForApprovalAccepted = $this->sikRepository->setWaitingForApproval($rtpo);

        if($waitingForApprovalAccepted)
        {
            return 'OK';
        }
        else{
            $this->sikRepository->rejectByRtpo($rtpo);
            return 'Rejected';
        }
    }
}

Sehingga implementasi pada controller menjadi seperti berikut:

/*
https://github.com/aufawibowo/semeru-api/blob/refactored/app/modules/rtpo/Presentation/Controllers/Controller.php
*/
public function requestMBPToSiteDownAction()
{
    $sik_no = $this->request->get('sik_no');
    $username = $this->request->get('username');
    $reason = $this->request->get('reason');
    $is_approved = $this->request->get('is_approved');

    $request = new ApproveRescheduleSIKRequest(
        $sik_no,
        $username,
        $reason,
        $is_approved
    );

    $service = new ApproveRescheduleSIKService(
        $this->di->get('sikRepository'),
        $this->di->get('rtpoRepository')
    );

    try {
        $result = $service->execute($request);

        $this->sendData($result);
    } catch (\Exception $e) {
        $this->handleException($e);
    }
}

2.2 Aktivitas Refactoring: Implementing OCP

Kategori: SOLID
Permasalahan: Penempatan perintah SQL yang digunakan untuk mengambil data pada satu tempat yang sama dengan handler request, response service, dan implementasi bisnis.
Solusi: Membuat object repository yang digunakan oleh service. Sehingga, jika terdapat kebutuhan tambahan yang akan datang dapat melakukan ekstensi tanpa merusak existing query yang sudah ada.

Potongan code sebelum refactoring

/*
https://github.com/aufawibowo/semeru-api/blob/2.9/app/Http/Controllers/RtpoControllerNew.php 1162
*/
public function approve_reschedule_sik(Request $request)
{
    //...

	if($is_approved){
	$approve = DB::table('propose_reschedule')
	->where('sik_no',$sik_no)
	->update([
		'status' => 1,
		'status_desc' => 'WAITING FOR NOS APPROVAL',
		'rtpo_nik' => $rtpo_nik,
		'rtpo_cn' => $rtpo_cn,
		'last_updated' => $date_now,
		'is_sync' => 0,
	]);

	$res['success'] = 'OK';
	$res['message'] = 'Success';
	
	return response($res); 
	}
	else{
	$approve = DB::table('propose_reschedule')
	->where('sik_no',$sik_no)
	->update([
		'status' => 2,
		'status_desc' => 'REJECTED BY RTPO',
		'reject_reason' => $reason,
		'rtpo_nik' => $rtpo_nik,
		'rtpo_cn' => $rtpo_cn,
		'last_updated' => $date_now,
		'is_sync' => 0,
		]);

	$res['success'] = 'OK';
	$res['message'] = 'Success';
	
	return response($res); 
	}
}

Potongan code setelah refactoring

<?php


namespace Semeru\Rtpo\Core\Domain\Repositories;


use Semeru\Rtpo\Core\Domain\Models\Rtpo;

interface SikRepository
{
    public function setWaitingForApproval(Rtpo $rtpo);
    public function rejectByRtpo(Rtpo $rtpo);
}

<?php


namespace Semeru\Rtpo\Core\Domain\Repositories;


interface RtpoRepository
{
    public function getRtpoUserData(string $username);
    public function getRtpoId();
}

2.3 Aktivitas Refactoring: Be strongly typed

Kategori: Clean Code / Defensive Coding
Permasalahan: Terkadang sebuah object creation dapat mengandung nilai yang tidak diharapkan.
Solusi: Dapat dibuat kelas sendiri, dalam konteks DDD, terdapat domain untuk setiap konteks

Potongan code sebelum refactoring

<?php


namespace Semeru\Rtpo\Core\Domain\Models;


class Rtpo
{
    private RtpoNik $rtpoNik;
    private string $rtpoCn;
    private SikNo $sikNo;
    private Date $last_updated;

    /**
     * Rtpo constructor.
     * @param RtpoNik $rtpoNik
     * @param string $rtpoCn
     * @param SikNo $sikNo
     * @param Date $last_updated
     */
    public function __construct(RtpoNik $rtpoNik, string $rtpoCn, SikNo $sikNo, Date $last_updated)
    {
        $this->rtpoNik = $rtpoNik;
        $this->rtpoCn = $rtpoCn;
        $this->sikNo = $sikNo;
        $this->last_updated = $lastUpdated;
    }

    /**
     * @return RtpoNik
     */
    public function rtpoNik(): RtpoNik
    {
        return $this->rtpoNik;
    }

    /**
     * @return string
     */
    public function rtpoCn(): string
    {
        return $this->rtpoCn;
    }

    /**
     * @return SikNo
     */
    public function sikNo(): SikNo
    {
        return $this->sikNo;
    }

    /**
     * @return Date
     */
    public function lastUpdated(): Date
    {
        return $this->lastUpdated;
    }


}

2.4 Aktivitas Refactoring: Implementing ISP

Kategori: SOLID
Permasalahan: Implementasi interface dapat digunakan oleh banyak query.
Solusi: Satu interface diimplementasikan oleh satu methode.

Potongan code

<?php


namespace Semeru\Rtpo\Core\Domain\Repositories;


interface RtpoRepository
{
    public function getRtpoUserData(string $username);
    public function getRtpoId();
}

<?php


namespace Semeru\Rtpo\Infrastructure\Persistence;


use Phalcon\Db\Adapter\Pdo\AbstractPdo;
use Semeru\Rtpo\Core\Domain\Repositories\RtpoRepository;

class SqlRtpoRepository implements  RtpoRepository
{
    private AbstractPdo $db;

    public function __construct(AbstractPdo $db)
    {
        $this->db = $db;
    }

    public function getRtpoUserData(string $username)
    {
        $sql = "select *
        from users
        where username = :username";

        $params = [
            'username' => $username
        ];

        return $this->db->fetchAll($sql, PDO::FETCH_ASSOC, $params);
    }

    public function getRtpoId()
    {
        $data = $this->getRtpoUserData();
        return $data['name'];
    }


}

2.5 Aktivitas Refactoring: Implementing DIP

Kategori: SOLID
Permasalahan: Perubahan bisnis jika ingin menggunakan database lain.
Solusi: Implementasi DIP pada AbstractPdo Phalcon

Potongan code

abstract class AbstractPdo extends AbstractAdapter
{
    return "sql adapter";
}

class SqlRtpoRepository implements RtpoRepository
{
    private AbstractPdo $db;

    public function __construct(AbstractPdo $db)
    {
        $this->db = $db;
    }
}

2.6 Aktivitas Refactoring: Naming Classes

Kategori: Clean Code
Permasalahan: Spaghetti Code didalam satu controller, dimana semua implementasi input/output handlers, implementasi bisnis, dan database query berada di dalam satu fungsi.
Solusi: Pemecahan berdasarkan metode domain driven design. Dimana object paling primitif adalah domain model.

Potongan code sebelum refactoring

menggunakan cuplikan kode yang sama dengan aktivitas refactoring 2.1.

Potongan code setelah refactoring

<?php


namespace Semeru\Rtpo\Core\Domain\Models;


class Rtpo
{

}

class Address
{

}

class Coordinate
{

}

class Date
{

}

2.6 Aktivitas Refactoring: Naming Method

Kategori: Clean Code
Permasalahan: Penamaan method tidak konsisten. Terdapat method yang menggunakan konvensi camelCase atau snake_case didalam satu kelas yang sama.
Solusi: Mengikuti best practice penamaan method PHP.

Potongan code sebelum refactoring

public function approve_reschedule_sik();
public function cekSamplingFormula();

Potongan code setelah refactoring

public function setWaitingForApproval();
public function rejectByRtpo();

2.7 Aktivitas Refactoring: Naming Method

Kategori: Clean Code
Permasalahan: Penamaan method tidak ambigu.
Solusi: Mengubah menjadi lebih singkat, padat, dan jelas.

Potongan code sebelum refactoring

public function tanggal_bulan_tahun_indo_tiga_char();

Potongan code setelah refactoring

public function getMonthInThreeCharacters();

2.8 Aktivitas Refactoring: Adding clean comments that convey intent

Kategori: Clean Code
Permasalahan: Terkadang pemberian nama metode sedikit menimbulkan multitafsir
Solusi: Menambah komentar yang menjelaskan fungsi tersebut.

Potongan code sebelum refactoring

public function getMonthInThreeCharacters();

Potongan code setelah refactoring

/**
* Function getMonth() return month in three character: Jan, Feb, Mar, etc.
* @return string
*/
public function getMonthInThreeCharacters(): string
{
    return $this->getMonth();
}

2.9 Aktivitas Refactoring: Removing zombie code

Kategori: Clean Code
Permasalahan: Zombie code merupakan cuplikan kode yang ditinggal dengan komentar sehingga tidak bisa dijalankan.
Solusi: Hapus kode.

Potongan code sebelum refactoring

// public function reject_reschedule_sik(Request $request)
// {
//   date_default_timezone_set("Asia/Jakarta");
//   $date_now = date('Y-m-d H:i:s');
//   $periode = date('Y-m');

//   $sik_no = $request->input('sik_no');
//   $reason = $request->input('reason');
//   $username = $request->input('username');

//   //$username = 'enggarrio';

//   $rtpo_users_data = DB::table('users')
//   ->select('*')
//   ->where('username',$username)
//   ->first();

//   $rtpo_nik = $rtpo_users_data->id;
//   $rtpo_cn = $rtpo_users_data->name;

//   $approve = DB::table('propose_reschedule')
//   ->where('sik_no',$sik_no)
//   ->update([
//     'status' => 2,
//     'status_desc' => 'REJECTED BY RTPO',
//     'reject_reason' => $reason,
//     'rtpo_nik' => $rtpo_nik,
//     'rtpo_cn' => $rtpo_cn,
//     'last_updated' => $date_now,
//     'is_sync' => 0,
//   ]);

//   $res['success'] = true;
//   $res['message'] = 'SUCCESS';
	
//   return response($res); 
// }

Potongan code setelah refactoring

kode dihapus

2.10 Aktivitas Refactoring: Fail fast

Kategori: Defensive Coding
Permasalahan: Semakin modular sebuah project (i.e. Clean Arch, Microservice), semakin kompleks cara untuk mentracing sebuah bug yang tercipta.
Solusi: Mereturn eksepsi sedini mungkin.

Cuplikan code

// app/modules/rtpo/Core/Application/Services/ApproveRescheduleSIK/ApproveRescheduleSIKService.php
public function execute(ApproveRescheduleSIKRequest $request)
    {
        $errors = $request->validate();

        if (count($errors) > 0) {
            throw new ValidationException($errors);
        }

2.11 Aktivitas Refactoring: Validating Null

Kategori: Defensive Coding
Permasalahan: Terkadang input bisa bernilai null. Proses validasi diperlukan.
Solusi: Membuat fungsi validasi null.

Cuplikan code

<?php


namespace Semeru\Rtpo\Core\Application\Services\ApproveRescheduleSIK;


class ApproveRescheduleSIKRequest
{
    public ?string $sik_no;
    public ?string $username;
    public ?string $reason;
    public ?string $is_approved;

    /**
     * ApproveRescheduleSIKRequest constructor.
     * @param string|null $sik_no
     * @param string|null $username
     * @param string|null $reason
     * @param string|null $is_approved
     */
    public function __construct(?string $sik_no, ?string $username, ?string $reason, ?string $is_approved)
    {
        $this->sik_no = $sik_no;
        $this->username = $username;
        $this->reason = $reason;
        $this->is_approved = $is_approved;
    }

    public function validate()
    {
        $errors = [];

        if (!isset($this->sik_no)) {
            $errors[] = 'sik no must be specified';
        }

        if (!isset($this->username)) {
            $errors[] = 'username must be specified';
        }

        if (!isset($this->reason)) {
            $errors[] = 'reason must be specified';
        }

        if (!isset($this->is_approved)) {
            $errors[] = 'is approved must be specified';
        }

        return $errors;
    }
}

2.12 Aktivitas Refactoring: Handling dates using date objects instead of strings

Kategori: Defensive Coding
Permasalahan: Input string dapat beraneka ragam.
Solusi: Object date membantu untuk mengimplementasi pembuatan object date dengan bersifat strong type.

Cuplikan code

public function execute(ApproveRescheduleSIKRequest $request)
    {
        $errors = $request->validate();

        if (count($errors) > 0) {
            throw new ValidationException($errors);
        }

        $rtpo = new Rtpo(
            $this->rtpoRepository->getRtpoId(),
            $this->rtpoRepository->getRtpoUserData(),
            new SikNo($request->sik_no),
            new \DateTime('now')
        );

    }

2.13 Aktivitas Refactoring: Positive conditionals

Kategori: Clean code
Permasalahan: Penamaan variabel boolean.
Solusi: Positive conditionals.

Cuplikan code

public function execute(AdminLoginRequest $request)
    {
        // validate request
        $errors = $request->validate();

        if (count($errors) > 0) {
            throw new ValidationException($errors);
        }

        // get user
        $user = null;

        if (is_numeric($request->id)) {
            $user = $this->userRepository->getByPhone($request->id);
        }

2.14 Aktivitas Refactoring: Removing defect log

Kategori: Clean code
Permasalahan: Logging yang tidak terpakai.
Solusi: Hapus defect log.

Cuplikan code yang dihapus

// $value_log = $this->saveLogSP1($sp_id, $user_nik, $user_cn, $status, $description, $image, $date_log);

2.15 Aktivitas Refactoring: Return early

Kategori: Clean code
Permasalahan: Sphagetti code
Solusi: Return early.

Cuplikan code

    if($waitingForApprovalAccepted)
    {
        return 'OK';
    }
    else{
        $this->sikRepository->rejectByRtpo($rtpo);
        return 'Rejected';
    }

2.16 Aktivitas Refactoring: Choosing the right exceptions

Kategori: Defensive coding
Permasalahan: Response message error yang beragam
Solusi: Menggunakan InvalidOperationException untuk operasi yang tidak berhasil ditemukan.

Cuplikan code

if (is_null($user)) {
    throw new InvalidOperationException('user_not_found');
}

// check if user administrator
if (!$user->isAdministrator()) {
    throw new InvalidOperationException('credentials_does_not_match');
}

// verify password
if (!$user->verifyPassword($request->password)) {
    throw new InvalidOperationException('credentials_does_not_match');
}

2.17 Aktivitas Refactoring: Removing warning code

Kategori: Clean coding
Permasalahan: Comment error namun fungsi tetap exist
Solusi: Dihapus atau dihapus komen kemudian dijalankan.

Cuplikan code yang dihapus

//ERROR
public function acceptDelayFromMbp($cancel_id, $user_id_rtpo, $username){

date_default_timezone_set("Asia/Jakarta");

2.18 Aktivitas Refactoring: Removing redundant comment

Kategori: Clean coding
Permasalahan: Comment yang redundat.
Solusi: Dihapus.

Cuplikan code yang dihapus

//bila cancel detil belum di tanda tangani maka
	if ($checkCancellationLetter!=null) {

		$supplyingPowerController = new SupplyingPowerController;
		$value_sp_log = $supplyingPowerController->saveLogSP1($checkCancellationLetter->sp_id, $checkCancellationLetter->id, $checkCancellationLetter->username, 'MBP_DELAY_FINISHED', 'user menyelesaikan delay mbpnya','' , '', $date_now);

2.19 Aktivitas Refactoring: Return empty collections instead of null

Kategori: Defensive
Permasalahan: Beberapa method mengubah state tanpa mengembalikan object apapun
Solusi: Mengembalikan dengan null

public function setDone(OrderId $orderId)
{
    $sql = "update orders set status = :status where id = :id";

    $params = [
        'status' => Order::STATUS_RECEIVED,
        'id' => $orderId->id(),
    ];

    $this->db->begin();
    $this->db->execute($sql, $params);
    $this->db->commit();

    return null;
}

2.20 Aktivitas Refactoring: Choosing the right exceptions

Kategori: Defensive
Permasalahan: Ada kemungkinan gagal menulis data ke database
Solusi: Menggunakan try and catch

public function setDone(OrderId $orderId)
{
    $sql = "update orders set status = :status where id = :id";

    $params = [
        'status' => Order::STATUS_RECEIVED,
        'id' => $orderId->id(),
    ];

    try {
        $this->db->begin();
        $this->db->execute($sql, $params);
        $this->db->commit();

        return true;
    } catch (\Exception $e) {
        var_dump($e->getMessage());
        $this->db->rollback();

        return false;
    }
}

2.21 Aktivitas Refactoring: Add unit test

Kategori: Automated Testing
Permasalahan: Terkadang terdapat kelalaian dalam pembuatan kelas seperti apakah kelas tersebut dapat menerima nilai null dsb
Solusi: Menambahkan unit test.

2.22 Aktivitas Refactoring: Removing apology comment

Kategori: Clean code
Permasalahan: Code yang hanya dicomment tapi tidak dikerjakan
Solusi: Diimplementasikan atau dihapus.

if ($updateMbp) {
    # kirim notif..:D mbp ini siap bertugas kembali
}
}

Name		Name	Last commit message	Last commit date
Latest commit History 210 Commits
app		app
public		public
tests		tests
.gitignore		.gitignore
.htaccess		.htaccess
cli.php		cli.php
composer.json		composer.json
composer.lock		composer.lock
phpunit.xml		phpunit.xml
readme.md		readme.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

refactoring

1. Daftar Project

2. Hasil Refactoring

2.1 Aktivitas Refactoring: Implementing SRP

2.2 Aktivitas Refactoring: Implementing OCP

2.3 Aktivitas Refactoring: Be strongly typed

2.4 Aktivitas Refactoring: Implementing ISP

2.5 Aktivitas Refactoring: Implementing DIP

2.6 Aktivitas Refactoring: Naming Classes

2.6 Aktivitas Refactoring: Naming Method

2.7 Aktivitas Refactoring: Naming Method

2.8 Aktivitas Refactoring: Adding clean comments that convey intent

2.9 Aktivitas Refactoring: Removing zombie code

2.10 Aktivitas Refactoring: Fail fast

2.11 Aktivitas Refactoring: Validating Null

2.12 Aktivitas Refactoring: Handling dates using date objects instead of strings

2.13 Aktivitas Refactoring: Positive conditionals

2.14 Aktivitas Refactoring: Removing defect log

2.15 Aktivitas Refactoring: Return early

2.16 Aktivitas Refactoring: Choosing the right exceptions

2.17 Aktivitas Refactoring: Removing warning code

2.18 Aktivitas Refactoring: Removing redundant comment

2.19 Aktivitas Refactoring: Return empty collections instead of null

2.20 Aktivitas Refactoring: Choosing the right exceptions

2.21 Aktivitas Refactoring: Add unit test

2.22 Aktivitas Refactoring: Removing apology comment

About

Releases

Packages

Contributors 2

Languages

aufawibowo/semeru-api

Folders and files

Latest commit

History

Repository files navigation

refactoring

1. Daftar Project

2. Hasil Refactoring

2.1 Aktivitas Refactoring: Implementing SRP

2.2 Aktivitas Refactoring: Implementing OCP

2.3 Aktivitas Refactoring: Be strongly typed

2.4 Aktivitas Refactoring: Implementing ISP

2.5 Aktivitas Refactoring: Implementing DIP

2.6 Aktivitas Refactoring: Naming Classes

2.6 Aktivitas Refactoring: Naming Method

2.7 Aktivitas Refactoring: Naming Method

2.8 Aktivitas Refactoring: Adding clean comments that convey intent

2.9 Aktivitas Refactoring: Removing zombie code

2.10 Aktivitas Refactoring: Fail fast

2.11 Aktivitas Refactoring: Validating Null

2.12 Aktivitas Refactoring: Handling dates using date objects instead of strings

2.13 Aktivitas Refactoring: Positive conditionals

2.14 Aktivitas Refactoring: Removing defect log

2.15 Aktivitas Refactoring: Return early

2.16 Aktivitas Refactoring: Choosing the right exceptions

2.17 Aktivitas Refactoring: Removing warning code

2.18 Aktivitas Refactoring: Removing redundant comment

2.19 Aktivitas Refactoring: Return empty collections instead of null

2.20 Aktivitas Refactoring: Choosing the right exceptions

2.21 Aktivitas Refactoring: Add unit test

2.22 Aktivitas Refactoring: Removing apology comment

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages 0

Contributors 2

Languages

Packages