-
Got these Composer warnings with AdminNeo 4-15. I am using |
Beta Was this translation helpful? Give feedback.
Answered by
peterpp
Feb 26, 2025
Replies: 1 comment
-
|
This is the result of Adminer's code architecture. It uses the same class names in each database driver and includes only one set based on the current connection. So warnings are expected, you can ignore them for now. I would like to change this approach in the future. I already tried to differentiate the class names for Adminer and Editor, but I didn't find an easy solution because of the plugin interface. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
wintstar
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the result of Adminer's code architecture. It uses the same class names in each database driver and includes only one set based on the current connection. So warnings are expected, you can ignore them for now. I would like to change this approach in the future.
I already tried to differentiate the class names for Adminer and Editor, but I didn't find an easy solution because of the plugin interface.