-
Notifications
You must be signed in to change notification settings - Fork 26
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
[IMPORT] feat: create and set import buttons #387
base: feat/import-monitoring
Are you sure you want to change the base?
[IMPORT] feat: create and set import buttons #387
Conversation
*ngIf="this.canImport" | ||
color="primary" | ||
class="btn-action uppercase float-right" | ||
[routerLink]="['/import']" |
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 faut que la redirection dirige vers la page de création d'un import
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.
traité.
frontend/app/components/monitoring-lists/monitoring-lists.component.ts
Outdated
Show resolved
Hide resolved
|
||
// medias; | ||
canCreateChild: { [key: string]: boolean } = {}; | ||
toolTipNotAllowed: string = TOOLTIPMESSAGEALERT; | ||
|
||
public userCruved: 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.
Uniquement utilisée dans le ngOnInit
... à supprimer pour moi
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.
traité.
// get user cruved | ||
const currentModule = this._moduleService.currentModule; | ||
this.userCruved = currentModule.module_objects.MONITORINGS_SITES.cruved; | ||
let cruvedImport: 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.
let cruvedImport: any = {}; | |
let cruvedImport: any = {C:0}; |
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.
traité.
|
||
// get user cruved | ||
const currentModule = this._moduleService.currentModule; | ||
this.userCruved = currentModule.module_objects.MONITORINGS_SITES.cruved; |
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 ne pas passer directement par le cruvedStore ?
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.
traité.
5342af3
to
86562cd
Compare
Tous les retours ont été traités |
Co-authored-by: Jacques Fize <[email protected]>
f61026c
to
f47a1e7
Compare
[IMPORT][MONITORING] IM_INIT_FROM_DEST_1 - Intégrer des boutons à l'interface de monitoring : https://github.com/orgs/PnX-SI/projects/13/views/6?pane=issue&itemId=83488034
A discuter :
est-ce utile de renvoyer id_base_site et id_dataset en queryParams pour le bouton situé dans la liste des observations (id_dataset peut être requêté directement à partir de l'id_base_visit, donc évite un check puisque si on l'envoie avec les queryParams il faudra vérifier de toute façon si l'id_dataset existe et est bien associé à la visite)