-
Notifications
You must be signed in to change notification settings - Fork 34
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
V8 support #34
Comments
Hi @gsdias There is no support for v8 yet, two reasons being the IFileSystem interface has changed slightly and new IoC infrastructure changes how custom IFileSystem implementations are registered. There is already work done on this in the v8-dev branch by but no means is it finished. Please feel free to lend a helping hand. |
Is it worth checking how this guys did it?
https://our.umbraco.com/packages/collaboration/umbracofilesystemprovidersazure/
And I managed to make it work from this source
https://our.umbraco.com/packages/collaboration/umbraco8-simple-aws-s3/
(the upload to s3 flow, not the reading from s3 like virtual provider)
I have a developer working in a possible solution already. I just wanted
to know what else can I do to support him. Any feedback from someone
already into this problem so he could pick up in the right direction.
…On 2019-05-29 08:44, Elijah Glover wrote:
Hi @gsdias [1]
There is no support for v8 yet, two reasons being the IFileSystem interface has changed slightly and new IoC infrastructure changes how custom IFileSystem implementations are registered. There is already work done on this in the v8-dev branch by but no means is it finished. Please feel free to lend a helping hand.
--
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [2], or mute the thread [3].
--
Best regards,
Goncalo Silva Dias
http://www.gsdias.pt - http://h-tracker.com
Links:
------
[1] https://github.com/gsdias
[2]
#34?email_source=notifications&email_token=AANEDUCKO7NV7C74AG4L7QTPXYC2XA5CNFSM4HQAZT3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOEVBQ#issuecomment-496781958
[3]
https://github.com/notifications/unsubscribe-auth/AANEDUBX7TNNIEVENCEZP2LPXYC2XANCNFSM4HQAZT3A
|
I haven't had time to update this package to be compatible with v8 as yet. I'm familiar with @JimBobSquarePants Azure provider implementation, it should only take a few hours of full focus. |
Great. What can I do to help you out? Any hint where I should look to get a faster solution and submit a PR?
…Sent from my iPhone
On May 29, 2019, at 16:41, Elijah Glover ***@***.***> wrote:
I haven't had time to update this package to be compatible with v8 as yet. I'm familiar with @JimBobSquarePants Azure provider implementation, it should only take a few hours of full focus.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Also happy to do some testing when the time comes. |
@ElijahGlover It sets up the component and composer which are the new features in 8.
I will improve this if I get the time, but I'm hoping you get a chance to look at it too. |
Can I know when is the v8 being supported by this package? I think READ.ME is outdated as when implementing changes to Global.asax.cs it breaks and FileSystemProvider no longer exists in v8.
The text was updated successfully, but these errors were encountered: