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
Right now we have completely confusing naming between our Settings components which contain the definition for the ColumnLayout containing the action items that can configure the option; and our Settings pages, which contain the definition for the Page that will contain said setting component
For example:
The file pages/settings/SettingsConnection.qml is a page and inside of here we have a component called ConnectionSettings which resides at components/ConnectionSettings.
SettingsConnection <-> ConnectionSettings
These are the same words, but in reverse order. We need a better naming system; or really a better implementation method.
The text was updated successfully, but these errors were encountered:
Right now we have completely confusing naming between our Settings components which contain the definition for the ColumnLayout containing the action items that can configure the option; and our Settings pages, which contain the definition for the Page that will contain said setting component
For example:
The file
pages/settings/SettingsConnection.qml
is a page and inside of here we have a component calledConnectionSettings
which resides atcomponents/ConnectionSettings
.SettingsConnection
<->ConnectionSettings
These are the same words, but in reverse order. We need a better naming system; or really a better implementation method.
The text was updated successfully, but these errors were encountered: