-
Notifications
You must be signed in to change notification settings - Fork 0
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
Evol/log api #6
base: evol/drawer
Are you sure you want to change the base?
Evol/log api #6
Conversation
disabled={disabled ?? false} | ||
onBlur={onBlurCombined} | ||
/> | ||
<Icon>arrow_forward</Icon> |
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.
c'est une icône material ça ? est-ce qu'il vaut pas mieux utiliser un composant qui contient l'icône spécifique plutôt qu'utiliser le composant Icon, puis spécifier dedans le type d'icone ?
import ArrowForwardIcon from '@mui/icons-material/ArrowForward';
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.
pour l'instant on utilise pas icons-material non
logApiLoader.isLoading | ||
&& ( | ||
<div> | ||
Loding |
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.
- i18n
- Loading
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.
oh l'oubli ! bien vu
|
||
$log-api-ok: #49cc90; | ||
$log-api-warning: #fca130; | ||
$log-api-error: #f93e3e; |
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.
On pourrait reprendre les couleurs qu'on a déjà non ? Et limite eclaircir ou foncer ?
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.
Il faudrait aussi déclarer les variable dans le scope de log api, sinon elles sont globales
.data { | ||
display: flex; | ||
width: 15%; | ||
height: 40px; |
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.
ça doit dépendre de la taille de la police je pense
@@ -56,6 +56,19 @@ export default function Navigation() { | |||
</NestedListItem> | |||
) | |||
} | |||
{ | |||
sessionService.hasPermission(Permission.MANAGE_SYSTEM) |
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.
La permission c'est pas plutôt MANAGE_API_LOGS ? Ou les deux ?
* @param selectedValue the map of the current selected value by the key filter | ||
* @constructor | ||
*/ | ||
function SingleChoiceFilterMenu( |
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.
Même remarque que sur l'autre MR avec react table.
Il faut bien faire l'UI je suis d'accord, par contre pour la logique on pourrait reprendre ce qui a été fait sur react table je pense
constructor(private readonly httpClient: PlumeAdminHttpClient) { | ||
} | ||
|
||
fetchAll(apiParam: LogApiParams) { |
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.
C'est plutôt search
non ?
const fetchLogById = () => { | ||
logApiLoader.monitor( | ||
logApiApi.fetchById(logApiId) | ||
.then(setLogApiDetail), |
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.
En cas d'erreur ?
logApiLoader.isLoading | ||
&& ( | ||
<div> | ||
Loading |
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.
I18n
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.
Et puis on a un composant loader non ?
@@ -43,3 +46,18 @@ export type SelectOptionProps = { | |||
label: string, | |||
value: string, | |||
}; | |||
|
|||
type GenericInputDateProps = { |
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.
Pourquoi mettre Generic devant ? Les autres composants sont pas génériques ? :O
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.
Ah c'est les trucs de base, dans ce cas appelle le type plutôt BaseInputDateProps
import useTimeout from '../plume-http-react-hook-loader/timeoutHook'; | ||
|
||
/* eslint-disable-next-line @typescript-eslint/no-explicit-any */ | ||
export default function useDebounce(callback: () => void, delay: number, dependencies: any[]) { |
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.
autant utiliser unkown[]
ça évite d'avoir une exception eslint
import useTimeout from '../plume-http-react-hook-loader/timeoutHook'; | ||
|
||
/* eslint-disable-next-line @typescript-eslint/no-explicit-any */ | ||
export default function useDebounce(callback: () => void, delay: number, dependencies: any[]) { |
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.
ça serait bien de commenter le truc ! Et limite le mettre à côté de ses autres poto les hook
No description provided.