-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature/kas 2430 gebruik vergaderactiviteit codelist uit backend om keuzelijst op te stellen in frontend #1269
Conversation
…n/frontend-kaleidos into feature/KAS-2430-gebruik-vergaderactiviteit-codelist-uit-backend-om-keuzelijst-op-te-stellen-in-frontend
…viteit-codelist-uit-backend-om-keuzelijst-op-te-stellen-in-frontend
Damn, zie het ook gebeuren. |
…viteit-codelist-uit-backend-om-keuzelijst-op-te-stellen-in-frontend
I only realize now that the edit-meeting-modal can break the meeting data 😕 (not caused by this PR). There is no consideration for annex-meetings like in the new-meeting-modal. If the type of the meeting changes to 'Plan VV' the user does not get an option to select a main meeting. Going to create a new story to cover this. |
Otherwise, if it's still loading the tests will complain because they try to click the loading text instead of waiting
Will try to get the Jenkins setup to automatically pull the correct backend branch some other time.
Behold, working tests :) http://kal-kastaar.s.redpencil.io:8080/job/kaleidos/job/custom_frontend_backend_combination/183/ |
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.
properkes opgelost met concepts
Ik had na approven nog even twijfel of er niets ging stuk gaan bij legacy (gewoon de verschillende views, geen edits) maar dat werkt precies nog goed. |
Adds a code list for vergaderactiviteiten.
The data stored here is now pulled in from the backend. Wherever kind URIs were used, now Ember Data records are used (meeting now has a has-one relationship to meeting-kind, Utils::KindSelector uses records instead of URIs now)
A custom adapter for meeting-kind models was added to prevent multiple requests to the backend being sent.