-
Notifications
You must be signed in to change notification settings - Fork 1
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
WIP Mixiskra #12
base: master
Are you sure you want to change the base?
WIP Mixiskra #12
Conversation
} | ||
|
||
export interface AvialiableRole { |
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.
typo: AvailableRole
} | ||
|
||
export interface Entrie { |
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.
typo: Entry
@@ -140,6 +140,7 @@ export interface Resource extends BaseItem { | |||
'@name': string; | |||
'@type': string; | |||
'@uid': string; | |||
UID: string; |
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.
Guillotina resources do not have a UID
attribute
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.
Plone resources does not have @uid :')
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.
ok, so 2 options:
- Either me make both of them optional:
@uid'?: string;
UID?: string;
and in all our code, we will have to check which value exists.
- Either in the resource service, in
get
(and any method returning a resource) we normalize the data to renameUID
into@uid
. It could be done by a function we provide in the main app module, and we would provide it only when using Plone as backend.
I like the 2nd option :)
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 like 2nd Option also !
No description provided.