You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Generated/VedicAstrology/Dasha/Current/CurrentPostRequestBody.cs
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,8 @@ public partial class CurrentPostRequestBody : IAdditionalDataHolder, IParsable
15
15
{
16
16
/// <summary>Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well.</summary>
/// <summary>Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.</summary>
/// <summary>Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).</summary>
19
21
publicDate?Date{get;set;}
20
22
/// <summary>Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.</summary>
@@ -37,6 +39,7 @@ public partial class CurrentPostRequestBody : IAdditionalDataHolder, IParsable
/// <summary>Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.</summary>
/// <summary>Ayanamsa actually applied, in degrees. The precession offset subtracted from the tropical (sayana) longitude to get the sidereal (nirayana) one. Lahiri sits near 23 deg 43 min for a 1990 birth, KP-Newcomb near 23 deg 38 min.</summary>
26
+
publicdouble?Ayanamsa{get;set;}
27
+
/// <summary>Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.</summary>
/// <summary>Mahadasha (major planetary period) in the 120-year Vimshottari dasha cycle. Start and end dates are determined by Moon nakshatra at birth.</summary>
/// <summary>Sidereal (nirayana) longitude of the birth Moon in degrees, 0 to 360, measured in the ayanamsa frame reported below. This single value determines the birth nakshatra and therefore every dasha start and end date in this response. Compare it against a reference chart to reconcile any date difference at its source.</summary>
38
+
publicdouble?MoonLongitude{get;set;}
33
39
/// <summary>Birth Moon nakshatra number (1-27). This nakshatra determines the starting dasha lord in the Vimshottari 120-year cycle.</summary>
34
40
publicint?MoonNakshatra{get;set;}
35
41
/// <summary>Vimshottari dasha lord of the birth nakshatra. This planet rules the first Mahadasha in the native life cycle.</summary>
@@ -73,6 +79,22 @@ public partial class CurrentPostResponse : IAdditionalDataHolder, IParsable
/// <summary>Time remaining in the currently running Sookshma dasha (fourth level). Sookshma periods last days rather than months, so this value turns over quickly.</summary>
/// <summary>Sookshma dasha (sookshma antardasha), the fourth level of the Vimshottari dasha hierarchy. Each Pratyantardasha divides into 9 Sookshma periods running roughly 3 to 30 days each, the finest level exposed by this API and the one used for day-level event timing and muhurta style selection.</summary>
/// Instantiates a new <see cref="global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse"/> and sets the default values.
@@ -100,14 +122,19 @@ public virtual IDictionary<string, Action<IParseNode>> GetFieldDeserializers()
100
122
returnnewDictionary<string,Action<IParseNode>>
101
123
{
102
124
{"antardasha", n =>{Antardasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_antardasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_antardasha.CreateFromDiscriminatorValue);}},
125
+
{"ayanamsa", n =>{Ayanamsa=n.GetDoubleValue();}},
126
+
{"ayanamsaType", n =>{AyanamsaType=n.GetEnumValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_ayanamsaType>();}},
103
127
{"mahadasha", n =>{Mahadasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_mahadasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_mahadasha.CreateFromDiscriminatorValue);}},
128
+
{"moonLongitude", n =>{MoonLongitude=n.GetDoubleValue();}},
104
129
{"moonNakshatra", n =>{MoonNakshatra=n.GetIntValue();}},
105
130
{"nakshatraLord", n =>{NakshatraLord=n.GetEnumValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_nakshatraLord>();}},
106
131
{"nakshatraName", n =>{NakshatraName=n.GetStringValue();}},
107
132
{"pratyantardasha", n =>{Pratyantardasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_pratyantardasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_pratyantardasha.CreateFromDiscriminatorValue);}},
108
133
{"remainingInAntardasha", n =>{RemainingInAntardasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInAntardasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInAntardasha.CreateFromDiscriminatorValue);}},
109
134
{"remainingInMahadasha", n =>{RemainingInMahadasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInMahadasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInMahadasha.CreateFromDiscriminatorValue);}},
110
135
{"remainingInPratyantardasha", n =>{RemainingInPratyantardasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInPratyantardasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInPratyantardasha.CreateFromDiscriminatorValue);}},
136
+
{"remainingInSookshma", n =>{RemainingInSookshma=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInSookshma>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_remainingInSookshma.CreateFromDiscriminatorValue);}},
137
+
{"sookshmaDasha", n =>{SookshmaDasha=n.GetObjectValue<global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_sookshmaDasha>(global::RoxyApi.VedicAstrology.Dasha.Current.CurrentPostResponse_sookshmaDasha.CreateFromDiscriminatorValue);}},
111
138
};
112
139
}
113
140
/// <summary>
@@ -118,14 +145,19 @@ public virtual void Serialize(ISerializationWriter writer)
/// <summary>Theoretical start of this period, present ONLY when the birth date truncated it. The Vimshottari cycle is already running when a native is born, so the period in force at birth began earlier: startDate is clipped to the birth moment while this field keeps the real start. Its presence is also why the first period of a chart can contain fewer than 9 sub-periods, the earlier ones having finished before birth. Absent on every period that runs its full length.</summary>
/// <summary>Ruling graha of this Vimshottari dasha period. One of 9 planets in the Ketu-Venus-Sun-Moon-Mars-Rahu-Jupiter-Saturn-Mercury sequence.</summary>
/// <summary>Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.</summary>
0 commit comments