Merge branch 'issue-39-kpi-response' into 'main' (4388b75a) · Commits · IF3250_2022_25_SIMKPI / SIMKPI-Frontend · GitLab

Skip to content

GitLab

Explore

Sign in
Register

Primary navigation

Project

S

SIMKPI-Frontend
- Activity
- Members
- Labels
- Issues
  0
- Issue boards
- Milestones
- Wiki
- Environments
- Terraform modules
- Incidents
- Service Desk

Snippets Groups Projects

Admin message

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

IF3250_2022_25_SIMKPI
SIMKPI-Frontend
Commits
4388b75a

Commit 4388b75a authored 3 years ago by

Aulia Adila

Downloads
- Plain Diff

Merge branch 'issue-39-kpi-response' into 'main'

Issue 39 kpi response

See merge request !20

parents 5b42d510 c97db0ae

Changes 10

Hide whitespace changes

Inline Side-by-side

Showing

src/components/commentCard.vue 34 additions, 0 deletions

src/components/commentCard.vue
src/components/sidebar.vue 7 additions, 5 deletions

src/components/sidebar.vue
src/components/table-2.vue 11 additions, 3 deletions

src/components/table-2.vue
src/router/index.js 12 additions, 0 deletions

src/router/index.js
src/views/KpiCreate.vue 2 additions, 2 deletions

src/views/KpiCreate.vue
src/views/KpiManagerDetail.vue 16 additions, 16 deletions

src/views/KpiManagerDetail.vue
src/views/ManagerKaryawanDetail.vue 1 addition, 2 deletions

src/views/ManagerKaryawanDetail.vue
src/views/ManagerKpiIndex.vue 8 additions, 5 deletions

src/views/ManagerKpiIndex.vue
src/views/ResponseDetail.vue 144 additions, 0 deletions

src/views/ResponseDetail.vue
src/views/ResponseIndex.vue 119 additions, 0 deletions

src/views/ResponseIndex.vue

with 354 additions and 33 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment