-
Notifications
You must be signed in to change notification settings - Fork 603
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
[2302] put internal-session into DI system #2315
[2302] put internal-session into DI system #2315
Conversation
@@ -147,19 +135,19 @@ describe('SessionService', () => { | |||
it("is read from the session's content", function() { | |||
session.set('some', 'data'); | |||
|
|||
expect(sessionService.get('data')).to.eql({ some: 'data' }); | |||
expect(sessionService.get('data')).to.eql({ some: 'data', authenticated: {} }); |
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.
This is a valid change IMO since the internal-session initializes it's content
to { authenticated: {} }
while the test session proxy initialized an empty object instead.
@@ -808,11 +804,4 @@ describe('InternalSession', () => { | |||
}); | |||
}); | |||
}); | |||
|
|||
it('does not share the content object between multiple instances', function() { |
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.
It didn't make sense to me since there's only 1 session:main
in the app anyway? Which is even more true with us only looking it up once in session service.
7f2481a
to
7406501
Compare
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.
This looks great. Thank you!
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.
looks good at first glance, but my knowledge of the ESA codebase is quite limited 😅
Should we also take care of this deprecation or do that in a separate PR?
|
@snewcomer seems unrelated to the DI stuff, so I'd suggest to do that in a dedicated PR |
Thanks a lot @BobrImperator |
Thank you! Is there a new release for this? |
@Turbo87 or @sdebarros would you mind cutting a release that includes this please? |
🎉 Thank you @BobrImperator ! |
closes #2302