We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
"Should object/resources be called with Dokan or Dokany"?
The reason for this question was the history of the Dokany project. These resulted in a mixuture of naming classes, methods, etc...
To introduce a common, predictable pattern and ease developing and maintanance, all classes related to dokan-dev/Dokany are preceeded with Dokan.
Dokan
The text was updated successfully, but these errors were encountered:
Merge branch 'feature/#37-fixNamingConvention' into develop
6c5f9c7
closes #37
Unified naming-scheme of wrapper-classes
5204c3b
See: e340747 / dokan-dev#37
Unified naming scheme
45fe7a3
Renamed DokanyFileHandle to DokanFileHandle
01e50b1
Renamed EasyDokanyFileSystem to EasyDokanFileSystem
ff1d27e
No branches or pull requests
"Should object/resources be called with Dokan or Dokany"?
The reason for this question was the history of the Dokany project. These resulted in a mixuture of naming classes, methods, etc...
To introduce a common, predictable pattern and ease developing and maintanance, all classes related to dokan-dev/Dokany are preceeded with
Dokan
.The text was updated successfully, but these errors were encountered: