You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CommonVocabulary:
1. clears all entries
2. concatentates arrays of lexical entries into its own lexicon
3. defines new terms
4. provides all definitions
5. deletes single entries
6. declares whether a term already exists
7. returns a list of its lexicon's terms
8. serializes entries to HTML
9. serializes entries to JSON
#2
* feat(common-vocabulary): add lexical manager common-vocabulary
CommonVocabulary:
1. clears all entries
2. concatentates arrays of lexical entries into its own lexicon
3. defines new terms
4. provides all definitions
5. deletes single entries
6. declares whether a term already exists
7. returns a list of its lexicon's terms
8. serializes entries to HTML
9. serializes entries to JSON
#2
* docs(repo): add product-related docs
* test(coverage): complete coverage
All specs pass.
* ci(node): restrict node version >= 8
Build on macOS
#2,#4
* ci(windows): add build script
#2,#4
* ci(release): automate deployment
#2,#4
1. User story summary
As a product maintainer,
I need to control terms used to describe features and defects
In order to communicate change without ambiguity.
2. Acceptance criteria
LexicalEntry
accepts aterm
, i.e., a canonical word that represents something significant about the domain my product models.LexicalEntry
accepts adefinition
, i.e., a statement of the exact meaning of theterm
.LexicalEntry
may accept an optionalcategory
.LexicalEntry
may accept the valid conventional commit types that could describe the types of change applied to my product's characteristic.LexicalEntry
may acceptmeta
data, i.e., additional information that provides meaning in context.The text was updated successfully, but these errors were encountered: