Revert git reset --hard 🚑 TIL

Andy Chong — Mon, 23 Nov 2020 16:07:43 +0000

Do note that this does not apply if you did not commit your changes before you did git reset --hard Thanks jessekphillips!

1 day, you are updating your branch...

git pull origin/branch_name
# got merge request? Hmmm... I wonder why 🤔

And you saw that you have newer changes after merging it, compared to the origin.
So you want to just reset it to the same state as the origin, then you did

git reset --hard origin/branch_name

.
.
.
OH MY GOD!!! 😱
You realize that you got the merge request because you actually committed some changes! God knows when 😵.

So here's the git command that gonna save you!

Introducing Git reflog!

git reflog

some other commits...
39386b35 HEAD@{8}: some commit message
18cb2ce7 HEAD@{9}: the commit that I want to revert back to!
f9386b35 HEAD@{10}: some commit message
some other commits...

git reset HEAD@{9}

AND I just save your day! Just kidding, here's the answer that actually save our day!

Solve node-gyp build error due to PYTHONPATH

Andy Chong — Fri, 07 Feb 2020 09:54:25 +0000

Update

From node-gyp@5.1.0 onwards, python3 will be used for the build, therefore please follow the steps below, but replace the last step with

PYTHONPATH=python3 && npm i

Recently, I faced the problem where node-gyp rebuild failed due to PYTHONPATH is pointing to python3. This is due to python2 is being deprecated, and python now points to python3 by default. While node-gyp requires python2 to build.

To solve this on macOS, just make sure you reinstall python 2 and python 3 and point PYTHONPATH environment variable to python2.

# Only do this if `where python2` output nothing
brew uninstall --ignore-dependencies python2 python3
brew install python2 python3 


PYTHONPATH=python2 && npm i

DONE!

References

https://github.com/nodejs/node-gyp/issues/1643#issuecomment-456011575

Ruby on Rails Graphiti file attachment/file upload

Andy Chong — Sun, 29 Dec 2019 15:09:25 +0000

I have been using Graphiti gem to build the API for the upcoming product in PostCo. While it is great that it makes building JSON:API compliant API endpoints a breeze, and made API resource the first-class citizen, it still quite lacks some important features, which includes file attachment support. I will talk about Graphiti in some other time but right now lets dive into today's topic.

In this article, you will understand how to add the file attachment functionality into the Graphiti resource. I will cover 2 of the most popular file attachment libraries recently, Active Storage and Shrine, and I will be uploading the file in Base64 string format.

Assuming the User model file looks something like this, where it contains 2 attachments, an avatar photo, and an ID card photo.

class User < ApplicationRecord
  # some other codes
  User::ATTACHMENT_ATTRS = [:avatar, :id_card].freeze

  ## Active Storage
  User::ATTACHMENT_ATTRS.each do |attachment_attr|  
    has_one_attached :"#{attachment_attr}"
  end
  # or
  # has_one_attached :avatar
  # has_one_attached :id_card

  ## Shrine
  include ImageUploader::Attachment(:avatar)
  include ImageUploader::Attachment(:id_card)

  # some more codes
end


## Shrine
class ImageUploader < Shrine
  plugin :data_uri
end

Write

During POST and PUT API call, the Graphiti Resource will assign all the submitted attributes and save it. But both file attachment libraries do not support attaching files by assigning the attribute.

Therefore, we need to extract the attachment data out from the submitted attributes and attach them separately. Luckily, Graphiti exposes the persistence lifecycle hooks to allow developers to add in additional logic during persisting the data.

To achieve the goal, we overwrite the assign_attributes to do exactly what we need to, extract the attachment data and assign them separately!

class UserResource < ApplicationResource

  # some other codes...

  def assign_attributes(model_instance, attributes)
    attachments = extract_attributes(attributes)
    attach_data(model_instance, attachments)

    attributes.each_pair { |key, value| model_instance.send(:"#{key}=", value) }
  end

  private

  def attach_data(model_instance, attachments)
    attachments.each do |attribute, data|
      ## Active Storage
      model_instance.send(:"#{attribute}").attach(data: data)

      ## Shrine
      model_instance.send(:"#{attribute}_data_uri=", data)
    end
  end

  def extract_attachments(attrs)
    attachments = {}
    User::ATTACHMENT_ATTRS.each do |attachment_attr|
      attachment = attrs.delete(attachment_attr)
      attachments[attachment_attr] = attachment if attachment.present?
    end
    attachments
  end

  # some more codes

end

Read

To return the attachment's URL when reading, we simply check each attachment and return the URL if it is available.

class UserResource < ApplicationResource

  User::ATTACHMENT_ATTRS.each do |attachment_attr|
    attribute attachment_attr, :string do
      ## Active Storage
      attachment = @object.send(:"#{attachment_attr}")
      attachment.attached? ? rails_blob_path(attachment, only_path: true) : ''

      ## Shrine
      @object.send(:"#{attachment_attr}_url") || ''
    end
  end
  # other attributes...
  attribute :created_at, :datetime, writable: false
  attribute :updated_at, :datetime, writable: false

  # some other codes...

end

Here's what the final Resource code will look like:

class UserResource < ApplicationResource

  User::ATTACHMENT_ATTRS.each do |attachment_attr|
    attribute attachment_attr, :string do
      ## Active Storage
      attachment = @object.send(:"#{attachment_attr}")
      attachment.attached? ? rails_blob_path(attachment, only_path: true) : ''

      ## Shrine
      @object.send(:"#{attachment_attr}_url") || ''
    end
  end
  # other attributes...
  attribute :created_at, :datetime, writable: false
  attribute :updated_at, :datetime, writable: false

  def assign_attributes(model_instance, attributes)
    attachments = extract_attributes(attributes)
    attach_data(model_instance, attachments)

    attributes.each_pair { |key, value| model_instance.send(:"#{key}=", value) }
  end

  private

  def attach_data(model_instance, attachments)
    attachments.each do |attribute, data|
      ## Active Storage
      model_instance.send(:"#{attribute}").attach(data: data)

      ## Shrine
      model_instance.send(:"#{attribute}_data_uri=", data)
    end
  end

  def extract_attachments(attrs)
    attachments = {}
    User::ATTACHMENT_ATTRS.each do |attachment_attr|
      attachment = attrs.delete(attachment_attr)
      attachments[attachment_attr] = attachment if attachment.present?
    end
    attachments
  end
end

And Voilà! Now you can upload attachments through the Graphiti API!