Skip to content
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

[SDESK-6851] Refactor locking mechanism #1789

Merged
merged 14 commits into from
May 23, 2023

Conversation

MarkLark86
Copy link
Collaborator

No description provided.

@MarkLark86 MarkLark86 added this to the 2.7 milestone Apr 24, 2023
@MarkLark86 MarkLark86 changed the title [SDCP-667] Refactor locking mechanism [SDESK-6851] Refactor locking mechanism May 1, 2023
@MarkLark86 MarkLark86 marked this pull request as ready for review May 3, 2023 06:52
@@ -23,7 +22,7 @@ import {
getTimeZoneOffset,
} from '../../utils';

import planningApi from '../planning/api';
import planningApis from '../planning/api';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be good to have some more descriptive naming for this vs planningApi, it's not obvious what's the difference

client/api/locks.ts Outdated Show resolved Hide resolved
Copy link
Member

@petrjasek petrjasek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't consider that naming to be a blocker, but would be good to look at it at some point imo

@MarkLark86
Copy link
Collaborator Author

MarkLark86 commented May 22, 2023

I don't consider that naming to be a blocker, but would be good to look at it at some point imo

I completely agree. In this PR I changed all imports from actions/planning/api to use planningApis, and all internal API to use planningApi. Where as before it was a mixed bag between the two. So in the future we should be able to simply replace planningApis with whatever makes sense

@MarkLark86 MarkLark86 merged commit bf82c0a into superdesk:develop May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants