Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Align use of enums and typemap interfaces in core package #170

Open
woutermont opened this issue Aug 10, 2021 · 0 comments
Open

Align use of enums and typemap interfaces in core package #170

woutermont opened this issue Aug 10, 2021 · 0 comments
Labels
low priority This issue has low priority

Comments

@woutermont
Copy link
Contributor

woutermont commented Aug 10, 2021

Also keep a tighter naming convention:

  • Enums are named with multiples
    (e.g. SomeKindOfEvents = { A, B, C })
  • Types that aggregate the actual types of those objects are named singular
    (e.g. SomeKindOfEvent = AEvent | BEvent | CEvent)
  • Type map interfaces are named as such, since they are in fact not really used, but rather misused, as types
    (e.g. SomeKindOfEventMap)

┆Issue is synchronized with this Wrike Item by Unito

@woutermont woutermont added the low priority This issue has low priority label Aug 12, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
low priority This issue has low priority
Projects
None yet
Development

No branches or pull requests

1 participant