Great news @musa.demir We're looking forward to have this running, thanks
Hi @ismcagdas .
Yes, in root project folder we run: npx sb init
After installation finishes try to run it trought the command npm run storybook
Just created bug for this in github repository.
https://github.com/aspnetzero/aspnet-zero-core/issues/2032
Hi lads,
We are so busy here, but I will try to prepare a fork of the base solution with ADAL integration. We did this POC 4 months ago, and not sure if will work on latest version 6.x (we are still in 5.62). POC is based on this wrapper https://github.com/manishrasrani/ms-adal-angular6 for simplicty
But I guess a product version should be using directly Azure AD ADAL library ADAL for JS
Regards
Thanks
We did a POC using microsoft-adal-angular6 and it worked fine, but definitely, this is something we would be very interested to see as part of the framework.
If I use
Configuration.Settings.Providers.Add<TimingSettingProvider>();
then I can't change the default timezone in appsetting.config it's always UTC no matter if I add the setting there. My question is how TimingSettingProvider can be updated via Environmental config settings or appsettings.
That's great.. But I prefer not to having to wait 5 seconds or 100ms.. I think it's just ok for now if I intercept that call. That should be sufficient to pass the test. Thanks
//Mock Background Job an intercept queue
NotificationDistributionJobArgs calledNotification = null;
var fakeBackgroundJobManager = Substitute.For<IBackgroundJobManager>();
fakeBackgroundJobManager.EnqueueAsync<NotificationDistributionJob, NotificationDistributionJobArgs>(
Arg.Any<NotificationDistributionJobArgs>(),
Arg.Any<BackgroundJobPriority>()).Returns(callInfo =>
{
calledNotification = callInfo.Arg<NotificationDistributionJobArgs>();
return Task.CompletedTask;
});
LocalIocManager.IocContainer.Register(Component.For<IBackgroundJobManager>().Instance(fakeBackgroundJobManager).IsDefault());
...
//Asserts
calledNotification
.ShouldNotBeNull(); //
Definetly this recudes render time.. but is not good for debugging. I've added 2 scripts in my packages so I can run with and without sourceMap
"start-nosourcemap": "ng serve --sourceMap=false ...."
Ou sorry.. I didn't realize that in EFCore transactions are not supported for SQLite in-memory store. I'll try to see which are the limitations we have in this meaning.
https://docs.microsoft.com/en-us/ef/core/miscellaneous/testing/sqlite
Thanks