Conversation
/// Extension methods for <see cref="IDependencyScope"/> facilitating getting the services used by custom WebHooks. | ||
/// </summary> | ||
[EditorBrowsable(EditorBrowsableState.Never)] | ||
public static class DependencyScopeExtensions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too much service locator. Can these be properly injected?
Does this look more in line with the approach you would expect? |
Just a note about couple items that need input / review:
|
@@ -57,12 +57,14 @@ public static void ConfigureMapping(IApplicationBuilder app) | |||
/// <returns></returns> | |||
private static async Task ProcessWebHook(HttpContext context, string webHookReceiver, string id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change this into a proper middleware class so that dependencies can be injected once instead of being pulled out of the container manually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: Should I revise the entire thing to merge the managers into the middleware, Simplifying the entire model? Basically have Middleware > Receivers > Handlers? This feels like a much simpler approach and having been through enough now, this may make for a simpler solution.
Any further information / details regarding this? Does it need to get updated to the current dev branch / RC2? Is it a good time to do that, or should we hold off until it releases? |
I am sorry it takes so long. I have poked the 'core' folks but I think they are busy. Will try again. |
@@ -18,3 +18,5 @@ _[Ss]cripts | |||
*.dot[Cc]over | |||
*.pubxml | |||
*.zip | |||
/coresamples/CoreCustomSender/project.lock.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should just exclude all project.lock.json
files - no need to check them in for this repo.
/// Extension methods for <see cref="IDictionary{TKey,TValue}"/>. | ||
/// </summary> | ||
[EditorBrowsable(EditorBrowsableState.Never)] | ||
public static class DictionaryExtensions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All these extension methods types need to be internal. We don't want them "leaking out" of this assembly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Used anywhere?
I might just be misreading the SLN file, but are the names and paths of the projects here correct? Refers to: WebHooks.sln:145 in 1b1edb7. [](commit_id = 1b1edb7, deletion_comment = False) |
public class CustomFilterProvider : IWebHookFilterProvider | ||
{ | ||
private readonly Collection<WebHookFilter> filters = new Collection<WebHookFilter> | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formatting got messed up here.
Added WebHookNotification Classes
OK I've updated my fork with a bunch of new projects for the core stuff. I have a few questions that I need some input on.
|
Figured out my Resource Loading issue (https://github.com/dotnet/corefx/issues/8754) |
Registrars as Optional (Resolve on Demand) Custom Subscribe/Unsubscribe / Notification working
Ok - custom senders and receivers are working with all the same interfaces implemented. I have not made my way back to writing tests, but generally all the same tests as the .net project should be passing. Question for Henrik - I had not paid attention to the Registrars before. It doesn't look like any sample or other project implements them. Is that there just in case someone needs to do some additional verification? I also did not really get the point of the IdValidator along the same lines. Could those not be just consolidated into a single validator, and leave it up to the implementation to decide what to validate? I am heading out on Vacation till next Tuesday. If you guys can give this a bit of a review (Eilon) in the mean time, I will start on converting the tests, and look at updating the other receivers, which should not take too much effort to crank through. |
Updated Service Configuration with comments to show use
@rposener @HenrikFrystykNielsen Hey folks, no milestone here, but it looks like it's getting close? Is there an ETA for this PR to get merged? |
Well, I have had some time away where I was unable to work on it. Should be able to get more done soon. Kind of wish I could get some review from the asp.net core team to know if middleware is looking OK, and from Henrik based on questions above. Certainly is close - just want a little confidence I'm not severely overlooking something. If it's good, then we should be able to just start porting all the implementations and tests. Or perhaps, the team wants it to be a single project that targets both frameworks. If that is the case, a lot of refactoring is probably needed... Open to input, and would love some feedback. |
Should I just close this and let someone else start again? |
I really appreciate all the work you have put into it and I apologize for the lack of response. Part of it has been because core has been in flux but with core 1.0 out it should be possible to get a stable model together. I absolutely do want this to run on core but it has been difficult to get things to align. Let me chat with some of the core folks and see how we can bring your work forward. thanks! |
Any word on if and when this branch is going to be merged to master? We have a Webhook based running we are looking to Migrate to .net core. Thanks! |
+1 it would be awesome if we can start developing webhooks in .net core |
Any further update on this? It would be great if we could use WebHooks in .NET core |
I'm super excited for this! Any eta? |
Anyone try this yet? |
It seems no one is paying attention |
This would be very cool indeed |
We have a project were this would be very useful, hesitant to use it though because there doesn't appear to be much recent work done on the project, is work going to continue on the project? |
It is on the road map but the stars haven't aligned yet to make it come together. I will provide an update when that happens. Thanks! Henrik |
Anything on this yet? |
When can we expect to get WebHooks support in ASP.NET Core? This blog post says:
Could you share any more details on that? |
Closing this PR because we're going with #153 instead. Thanks! |
Webhook is not working for ASP.NET core 2.1 with GitHub. Does any one have any working samples. |
@ALMWEARE please log a new issue with details. |
Haven't had a lot of time to do much else, yet. Coming weeks should provide more options. Any chance you guys will be at Build event? Would like to see a V1 of this published as nupkg's by then. If you guys can provide some guidance / how IServiceCollection should/should not be used, etc. that would be helpful. Also, should it leverage the HttpRequest ApplicationServices property to do all resolution? Do we need the Default Service functionality, or should that be handled as a default during registration using an option lambda on the extension method for Configuring WebHooks?