Clarify how to store extension attributes in the database

Open Beginner friendly
#313 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
databases, documentation

Research direction

Open /guides/v2.4/extension-dev-guide/extension_attributes/adding-attributes.html and review the existing extension-attribute guidance. Check how db_schema.xml and an InstallSchema setup script are described, then clarify the required way to persist scalar extension-attribute values in the database; done when a developer can determine whether to create a table column and how.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched the existing issues
What's missing?

General issue

Affected topic: /guides/v2.4/extension-dev-guide/extension_attributes/adding-attributes.html
Description:

The article is not clarifying whether we should create our own table column for scalar attributes manually for example via db_schema.xml or via an InstallSchema setup script to persist the extension attribute value in the database.
Possible solutions:

Clarify what a developer needs to do to store the extension attribute in the database.
Additional information:

Dominant language
JavaScript
Stars
11
Forks
178
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AdobeDocs/commerce-php

All issues in AdobeDocs/commerce-php

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.