Feat: migrate back-end from old app #78 #101
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
relates to #78
WARNING: Changes to the data from previous version!
Sessions
Speakers are no longer an attribute of the model (i.e.
speaker1,speaker2, etc...) but an array of speakers, allowing us to have more speakers. However the Front-End will have to be adapted to this new structure.Session Registrations
We might possibly need to add more user information to this model (such as a
nameor a profile picture) to display the reigstered users in a session on the Front-End.The logic to check wether the session registration is open is no longer inside the model but will be added (by me) to the configurations model.
Users
We removed the CV data and actions as well as the social media links - at least for now. We might add LinkedIn in the future.
Map information such as address, latitute and longitude have been removed from the user model and will be added when the map feature is readded to this app version
Speakers
Check wether it is possible to update the Speaker crreation UI in the front-end to pass data from an exising user (like name and profile picture) to speed up the creation of the speakers and potentially linking speakers and users to their sessions
Connection
We removed the Summary and Profile classes from the user model as there is no longer as much sensitive information that we need to hide from the public. However in the future we might add new sensitive data that we should only display to connected users so I'll leave this here.
Tomorrow or the day after I'll create the individual issues for each front-end section.