Changes to Compatibility: Dashakoota (10-fold 39-point)
POST /vedic/compatibility/dashakoota
Every recorded change to this endpoint, newest first. Back to the operation
Changed in 4 of the 13 revisions of this API.81218
What changed
- ○
added the optional property
data/boyto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/doshasto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/girlto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/mahendra/distanceto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/mahendra/maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/mahendra/scoreto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/pointsto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/recommendationto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/thresholdto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/vedha/blockedto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/vedha/maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/vedha/scoreto the response with the200statusresponse-optional-property-added
- ○
- ○
added the new optional request property
chart1/ayanamsanew-optional-request-property
- ○
added the new optional request property
chart2/ayanamsanew-optional-request-property
- ○
- ●
the
chart1/timezoneOffsetrequest property's max was set to14.00request-property-max-set
- ●
the
chart2/timezoneOffsetrequest property's max was set to14.00request-property-max-set
- ●
the
chart1/timezoneOffsetrequest property's min was set to-14.00request-property-min-set
- ●
the
chart2/timezoneOffsetrequest property's min was set to-14.00request-property-min-set
- ●
- ▲
the request property
chart1/latitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
chart1/longitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
chart2/latitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
chart2/longitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
chart1/latitudebecame requiredrequest-property-became-required
- ▲
the request property
chart1/longitudebecame requiredrequest-property-became-required
- ▲
the request property
chart2/latitudebecame requiredrequest-property-became-required
- ▲
the request property
chart2/longitudebecame requiredrequest-property-became-required
- ●
the
chart1/latituderequest property's max was set to90.00request-property-max-set
- ●
the
chart1/longituderequest property's max was set to180.00request-property-max-set
- ●
the
chart2/latituderequest property's max was set to90.00request-property-max-set
- ●
the
chart2/longituderequest property's max was set to180.00request-property-max-set
- ●
the
chart1/latituderequest property's min was set to-90.00request-property-min-set
- ●
the
chart1/longituderequest property's min was set to-180.00request-property-min-set
- ●
the
chart2/latituderequest property's min was set to-90.00request-property-min-set
- ●
the
chart2/longituderequest property's min was set to-180.00request-property-min-set
- ○
the
latituderequest property default value0was removedrequest-property-default-value-removed
- ○
the
latituderequest property default value0was removedrequest-property-default-value-removed
- ○
the
longituderequest property default value0was removedrequest-property-default-value-removed
- ○
the
longituderequest property default value0was removedrequest-property-default-value-removed
- ▲