lbryio / lbryio/block-explorer

New User Setup - Naming Conventions for tables and columns

Open
#88 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
17
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Hello, I would like to contribute to this project and I am having a little trouble getting set up.

I noticed that in the code the database table names are lowercase singular like 'block' and 'claim' while in the database SQL file https://github.com/lbryio/block-explorer/blob/master/sql/lbryexplorer.ddl.sql that is supposed to be used to populate the database schema, the table names are capital and plural, like 'Blocks' and 'Claims'.

Also, similar things are going on for the column names such as 'TransactionHashes' in the database and 'transaction_hashes' in the code.

Is there something I am missing to get CakePHP to convert from one to the other automatically? Also, it seems that this is exactly opposite of their recommended conventions.

Any help would be appreciated. =)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Read sql/lbryexplorer.ddl.sql first, then compare its table and column names with the corresponding database usage in the project. Determine whether CakePHP maps the capitalized plural schema names to the lowercase singular names in code; done means the mismatch is explained and the expected naming convention or required change is clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, sql
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.