Updated SequenceExporter.java to grab the courseSequenceObject property from the request body rather than yearList. yearList is then grabbed from courseSequenceObject. Updated frontend accordingly.
Sequence provider now has a better name for its single response property (response --> courseSequenceObject). Also, it now responds differently when the sequence is not found ("Sequence ID not found" --> {}). Updated frontend accordingly.
Renamed coursesequences api url endpoint name to recommendedsequence. This will cause merge conflicts once #120 is merged.
Added two new json files to docs/. They will be linked to by the wiki in order to provide pretty-printed versions of the sample requests/responses.
Test
If you want to test you can double check that export and recommendedsequence are both still working on courseplannerd.
resolves #123
Please merge #120 and #121 before this guy
Summary
Updated
SequenceExporter.javato grab thecourseSequenceObjectproperty from the request body rather thanyearList.yearListis then grabbed fromcourseSequenceObject. Updated frontend accordingly.Sequence provider now has a better name for its single response property (
response-->courseSequenceObject). Also, it now responds differently when the sequence is not found ("Sequence ID not found"-->{}). Updated frontend accordingly.Renamed
coursesequencesapi url endpoint name torecommendedsequence. This will cause merge conflicts once #120 is merged.Added two new json files to
docs/. They will be linked to by the wiki in order to provide pretty-printed versions of the sample requests/responses.Test
If you want to test you can double check that
exportandrecommendedsequenceare both still working oncourseplannerd.