Forem: Akshay Khale

Share your GitHub Profile Readme Link

Akshay Khale — Fri, 18 Nov 2022 09:15:01 +0000

Hi All,

GitHub Profile Readme.md file is an excellent options for developers to showcase their achievements and sometimes event brag about their open source contribution.

I am requesting you all to share your GitHub profile Readme and let's make a curated list of creative ways of using this simple feature provided by GitHub.

Here is my GitHubProfile Readme: @akshaykhale1992

And Please share your's

Getting Started with NextJS13

Akshay Khale — Thu, 03 Nov 2022 11:24:31 +0000

In the last week, Varcel made a lot of announcements at their NextJS conference (NextConf), it was a fascinating event with some significant announcements and keynotes by our favorite Dev-YouTubers (or should I say Dev-tubers). Most of the announced products are still in the Beta and Alpha stages but that does not stop us from giving them a try.

Here are some significant announcements made during the conference:

The NextJS-13
Turbopack
Improvements to the @next/image
Improvements to the @next/link
and updated and faster Next Router.

Out of these new features/products, NextJS-13 got me excited since I am already using NextJS for some of my projects and I love their philosophy and their focus on the developer experience (DX) while designing the framework. So when I heard about NextJS13, I was super excited and wanted to give it a try.

After digging the internet on how to start with NextJS-13, I could not find solid documentation for the same. Next/docs do not contain documentation for Next-13 since it’s not stable yet but after googling and watching some youtube videos, I could find the link for their Beta documentation that has complete details of the NextJS-13, as to how to get started, what’s new and what’s same.

So let's get started with NextJS13

If you are starting with a new project then you can simply run:

// With npx
npx create-next-app@latest --experimental-app
// With yarn
yarn create next-app --experimental-app
// With pnpm
pnpm create next-app --experimental-app

If you want to continue with the existing project then you can simply run:

// With npm
npm i next@latest react@latest react-dom@latest eslint-config-next@latest
// With yarn
yarn add next@latest react@latest react-dom@latest eslint-config-next@latest

Note: If you are making changes to the existing project then it will work with the pages directory and not the experimental app directory, if you want to use the app directory instead of pages then you will have to make the following changes to your next.config.js file.

const nextConfig = {
  experimental: {
    appDir: true,
  },
};

module.exports = nextConfig;

After following all these steps you will have a NextJS 13 project up and running.

This article is a snippet from this article, I published on medium (don't worry it's not a members only article) where I shared about how to get started with NextJS13 and what are the changes and new improvements to NextJS13.

Thank you!!!

Password-based or Passwordless login, what do you prefer/recommend and why?

Akshay Khale — Sat, 25 Jul 2020 09:21:04 +0000

I am an advocate of Passwordless login, I recommend everyone to go passwordless, and rely on social logins but I would love to know the views of dev-community on the subject.

Are we losing the Basics???

Akshay Khale — Mon, 29 Jun 2020 14:31:51 +0000

Being in the Tech field, We are "Standing on the shoulders of giants". Our IDEs are powerful in fact normal Text-Editors are also Powerful with thousands of extensions making coding as simple as possible.

So, do you think that being surrounded by all these powerful tools, we are losing the basics?

An ancient example:

Since we have phonebooks we don't remember anyone's phone number anymore.

A simple way to debug PHP applications.

Akshay Khale — Sun, 28 Jun 2020 09:08:45 +0000

The Problem:

Debugging can be irritating sometimes and when it comes to debugging server-side code, it's can be daunting. Printing the variable values, stopping the execution, and then continue, sometimes it takes hours. In Client-side languages like Javascript, it's pretty simple, you just do a console.log and wait for the complete page to render without stopping.

Solution:

That was my inspiration behind creating console-logger.
A simple PHP library that can be installed using composer and get you started with logging details in your browser console.

How to use it?

Install the package using composer

composer require akshaykhale1992/console-logger

Start using it...

Simple Example:

<?php
include './vendor/autoload.php';
use consoleLogger\Logger;
(new Logger())->emergency("This is from Server Side");

Available Functions:

Logger Function	Equivalent Console Log
`(new Logger())->emergency`	`console.error`
`(new Logger())->alert`	`console.warn`
`(new Logger())->critical`	`console.error`
`(new Logger())->error`	`console.error`
`(new Logger())->warning`	`console.warn`
`(new Logger())->notice`	`console.log`
`(new Logger())->info`	`console.info`
`(new Logger())->debug`	`console.debug`
`(new Logger())->group`	`console.group`
`(new Logger())->groupEnd`	`console.groupEnd`

The consoleLogger\Logger class follows PHP PSR-3: Logger Interface standards and implements all the functions for your specific needs.

I hope it will be useful for you and it's an open-source project so please feel free to tag along by creating issues or by adding new features.

Best.

Composer Package Development tips and tricks

Akshay Khale — Wed, 24 Jun 2020 15:31:46 +0000

If you are a PHP developer and do active PHP Development then there are a lot of chances that you would want to develop a Package and use it in your application.

This is a very short article (rather a tip) which will help you with package development.

If you have your package ready, with PSR-4 Autoloading and you do not want to publish it on Packagist or simply want to test it on your development environment then simply you can use composer repositories option.

Just add following code in your composer.json file where you want to use the package.

"require": {
    ....
    "<vendor-name>/<package-name>": "dev-master",
    ....
},
"repositories": [
    {
        "type": "vcs",
        "url": "git@github.com:<vendor-name>/<repository-name>.git"
    }
],

It will auto-pull the Package from Github (or any other VCS) and set it up for you to start with your development (provided you have repository access).

I was following the same and it worked flawlessly multiple developers were working on the Package and it worked like magic but then there was another catch, I wanted to avoid pushing on git and wanted to test the package in an application. composer to the rescue, composer allows local path in repository like this:

"require": {
    ....
    "<vendor-name>/<package-name>": "dev-master",
    ....
},
"repositories": [
    {
        "type": "path",
        "url": "/Users/user/package"
    }
],

It worked but the problem was before pushing the code, I had to make changes from VCS to Path in the calling application’s composer file. which was a pain, I tried searching options for commenting in composer.json file or some other options where I can keep the local and production environment together. The internet spoke the truth, No, there is no way to comment in composer.json file. but I found a work-around on stackoverflow.

Apparently, you can have multiple composer.json files in your PHP application and you can mention it run-time, which one to use for installing packages.

you can do:

    composer install // or composer update

which will install the packages from composer.json file and you can do

    COMPOSER=composer-local.json composer install // or composer update

which will load the packages from composer-local.json file.

Hope these tricks will be useful for you.

Thank you for reading.

Happy coding!!!

Originally published on Medium

A simple Database Suggestion

Akshay Khale — Tue, 03 Mar 2020 05:17:59 +0000

If you have been doing software development then you might have encountered a situation where you would want to deactivate a user account or mark some actions as done, where you might be using Boolean Data-type to store those actions.

E.g.

If you want to deactivate then you might have been setting boolean is_active field to true for active users and false for in-active users.

If you want to save notification status for an order then you might have been using email_status as a boolean field with default value as false which you change it to true when the email status is shared with the customer.

The approach above is completely fair and it works but there is a problem in the above approach. It does not have a record of exactly when the user was deactivated or exactly when the email_status was sent to the customer.

For that most of the developers follow a simple approach, instead of using boolean field is_active they use activated_on (or deactivated_on depends on your business requirement) Date field with default value as NULL. They use the following queries to find users:

View on Gist

I am not saying this is the best approach but it surely help you to make more sense out of the data in the Database and it completely depends on your business requirements.

That’s all folks!!!

Thank you for reading :) :) :)

Originally Published on Medium: A simple Database Suggestion

Follow me on my social media profiles:
Twitter@TheAkshayKhale
Fb@TheAkshayKhale
Medium@TheAkshayKhale

GitHub: AkshayKhale1992