BeaconCMS/beacon

Content API - only save if there are actual changes

Open

#620 opened on Oct 24, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (120 forks)batch import
area:contentenhancementgood first issue

Repository metrics

Stars
 (1,194 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

For every "update" action on the Content API it should check if there are actual differences between the latest saved version and the data being updated and skip if the data is equal.

  • Do not trigger the loading mechanism that demands server resources
  • Save DB resources by not inserting unnecessary data

Contributor guide

Research direction
Implement a diff check between the existing saved data and the incoming update data in the Content API. If no differences are found, skip the save and avoid triggering server side reloading or inserting into the database.
Tech stack
elixir
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ElixirPhoenix
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65