Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Added a synonyms attribute to several entity classes. This is an array of synonym names that are used for matching text typed by the user on the front end, so that the synonym they typed can be replaced with the entity's actual name.
For example, lecturer or teacher would be replaced with Professor.
The get route is called entity_structure and retrieves those synonyms, as well as the names of all the columns for each entity so that we can perform autocomplete with column names as well.
Type of change (pick-one)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration (hardware/operating system/etc).
Ran get requests on Postman to verify that the correct data was being fetched.
Checklist (check-all-before-merge)
formatting help: - [x] means "checked' and - [ ] means "unchecked"
What's New?
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Added a synonyms attribute to several entity classes. This is an array of synonym names that are used for matching text typed by the user on the front end, so that the synonym they typed can be replaced with the entity's actual name.
For example,
lecturer
orteacher
would be replaced withProfessor
.The get route is called
entity_structure
and retrieves those synonyms, as well as the names of all the columns for each entity so that we can perform autocomplete with column names as well.Type of change (pick-one)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration (hardware/operating system/etc).
Ran get requests on Postman to verify that the correct data was being fetched.
Checklist (check-all-before-merge)
formatting help:
- [x]
means "checked' and- [ ]
means "unchecked"[ ] I documented my code according to the Google Python Style Guide
[ ] I ran
./build_docs.sh
and the docs look fine[ ] I ran
./type_check.sh
and got no errors[ ] I ran
./format.sh
because it automatically cleans my code for me 😄[ ] I ran
./lint.sh
to check for what "format" missed[ ] I added my tests to the
/tests
directory[ ] I ran
./run_tests.sh
and all the tests pass