Skip to content

Evaluate to refactor all classes #197

New issue

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

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

Already on GitHub? Sign in to your account

Open
mfranzke opened this issue Nov 23, 2022 · 1 comment
Open

Evaluate to refactor all classes #197

mfranzke opened this issue Nov 23, 2022 · 1 comment
Labels
question Further information is requested
Milestone

Comments

@mfranzke
Copy link
Member

mfranzke commented Nov 23, 2022

Either replace or prepend all existing namespaces of elm-/cmp-/rea- (and possible future tpl- for templates, all of which inform the users of their types) by another namespace (e.g. db-).

@mfranzke mfranzke added the question Further information is requested label Nov 23, 2022
@mfranzke mfranzke added this to the Guidelines 3.0 milestone Nov 23, 2022
@d-koppenhagen
Copy link
Contributor

I would really love to see only the prefix / namespace db- instead of all the different ones we have by now.
The reason: it makes it way more recognizable as developers must only remember the db- namespace.
As a consumer of DB UI Core it's not important for me to reflect the category of the element in the namespace. I want to use elements easily without thinking about what type of element I am using.

Probably there could be a transition phase where already the new namespaces are available but the old ones are still supported to migrate smoothly step-by-step. Otherwise the Breaking Change should be documented well with detailed migration instructions (or even a script / regex for helping to search/replace)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants