I was looking at these new providers and found the FileSystemProvider. Great was my first thought, something to replace the missing functionality of Hive providers from Umb5.
Almost, somewhere someone descided to make the bases of this provider internal
So I downloaded the sources of 6.0.0 and found the same results.
Question
Are there any plans to make this provider public? I'd say that it would be really neat to have it that way. If not your should really stop calling this module a "provider".
I hear your frustration ... at the moment the decision to mark certain new classes/interfaces/methods as "internal" is that they are currently subject to change - which can be managed with the core codebase, but would be a nightmare for 3rd-party developers.
I believe once the API has been decided and agreed (lots of talk on the mailing list at the moment), then they will be marked as "public".
Why o why is IFileSystem internal?
I was looking at these new providers and found the FileSystemProvider. Great was my first thought, something to replace the missing functionality of Hive providers from Umb5.
Almost, somewhere someone descided to make the bases of this provider internal
So I downloaded the sources of 6.0.0 and found the same results.
Question
Are there any plans to make this provider public? I'd say that it would be really neat to have it that way. If not your should really stop calling this module a "provider".
:)
Hi Eric,
I hear your frustration ... at the moment the decision to mark certain new classes/interfaces/methods as "internal" is that they are currently subject to change - which can be managed with the core codebase, but would be a nightmare for 3rd-party developers.
I believe once the API has been decided and agreed (lots of talk on the mailing list at the moment), then they will be marked as "public".
Cheers, Lee.
Thanks Lee, excellent future I hear! :)
Is this any closer? We're looking at this at the moment to run on AWS, so writing an S3 provider is key.
I believe that IFileSystem will be made public in v6.0, (it is still marked as internal for v4.11).
The best place to keep track on this issue is here: http://issues.umbraco.org/issue/U4-1156
Cheers, Lee.
is working on a reply...