Open andyl opened 6 years ago
Currently we have statement fields which are used in Issue, Offer, and Contract.
statement
Issue
Offer
Contract
stm_title
stm_body
stm_issue_uuid
stm_tracker_uuid
stm_status
The statement field names are the same across all classes, but the purpose differs:
For our field-names to be more intention revealing, probably it would be good to either:
src_title
match_title
I like both rename suggestions equally well, maybe do both?
Currently we have
statement
fields which are used inIssue
,Offer
, andContract
.stm_title
stm_body
stm_issue_uuid
stm_tracker_uuid
stm_status
The statement field names are the same across all classes, but the purpose differs:
Issue
- holds the source dataOffer
andContract
- query values used to match and evaluateFor our field-names to be more intention revealing, probably it would be good to either:
Issue
(egstm_title
->src_title
)Offer
andContract
(egstm_title
->match_title
)