@roxyapi/ui 0.15.0 → 0.15.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const ROXY_UI_VERSION = "0.15.0";
1
+ export declare const ROXY_UI_VERSION = "0.15.1";
2
2
  //# sourceMappingURL=version.d.ts.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@roxyapi/ui",
3
- "version": "0.15.0",
3
+ "version": "0.15.1",
4
4
  "description": "Web components for the RoxyAPI catalog. Drop-in charts, tables, cards, forms for astrology, tarot, numerology, biorhythm, I Ching, crystals, dreams, angel numbers, and more. One key, beautiful in 30 minutes.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",
@@ -58,9 +58,10 @@ function chain(values: ReadonlyArray<string | number>): string {
58
58
  }
59
59
 
60
60
  /**
61
- * KP (Krishnamurti Paddhati) chart. Renders /vedic-astrology/kp/chart: the
62
- * Ascendant with its full stellar hierarchy, a planets-and-nodes table, a
63
- * Placidus cusps table, and the significator tables.
61
+ * KP (Krishnamurti Paddhati) chart. Renders /vedic-astrology/kp/chart: an
62
+ * Ascendant summary, a planets-and-nodes table, a Placidus cusps table, and the
63
+ * significator tables. The Ascendant is cusp 1, so its full four-lord chain is
64
+ * already the first row of the cusps table and the header stays a summary.
64
65
  *
65
66
  * @remarks
66
67
  * The cusp and planet sub lords are the primary predictive surface in KP, so
@@ -216,6 +217,7 @@ export class RoxyKpChart extends RoxyDataElement<KpChartResponse> {
216
217
  starLord: node.starLord,
217
218
  subLord: node.subLord,
218
219
  subSubLord: node.subSubLord,
220
+ kpNumber: node.kpNumber,
219
221
  retrograde: true,
220
222
  });
221
223
  }
package/src/manifest.ts CHANGED
@@ -248,10 +248,11 @@ export const ROXY_COMPONENTS: readonly RoxyComponent[] = [
248
248
  slug: 'kp-chart',
249
249
  heading: 'KP chart',
250
250
  description:
251
- 'Full KP chart with Ascendant, Placidus cusps, and planets in tabbed stellar-hierarchy tables',
251
+ 'Full KP chart with Ascendant, Placidus cusps, and planets and nodes in tabbed stellar-hierarchy tables',
252
252
  docsLabel: 'Vedic (KP)',
253
253
  endpointLabel: 'POST /vedic-astrology/kp/chart',
254
- docsSummary: 'Ascendant, cusps, and planets with KP stellar hierarchy',
254
+ docsSummary:
255
+ 'Ascendant, cusps, planets and nodes with KP stellar hierarchy',
255
256
  topic: 'Vedic',
256
257
  },
257
258
  {
@@ -3960,6 +3960,10 @@ export type KpChartResponse = {
3960
3960
  * Zodiac sign of the Ascendant.
3961
3961
  */
3962
3962
  sign: string;
3963
+ /**
3964
+ * Ruling planet of the Ascendant sign (the rashi lord). In KP this is the weakest of the four lords, ranked below the star lord and sub lord, but it still sets the broad temperament of the Lagna.
3965
+ */
3966
+ signLord: string;
3963
3967
  /**
3964
3968
  * Nakshatra (star) of the Ascendant.
3965
3969
  */
@@ -4127,6 +4131,10 @@ export type KpChartResponse = {
4127
4131
  * KP sub-sub lord (SSL) of Rahu.
4128
4132
  */
4129
4133
  subSubLord: string;
4134
+ /**
4135
+ * KP number (1-249) locating Rahu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
4136
+ */
4137
+ kpNumber: number;
4130
4138
  };
4131
4139
  /**
4132
4140
  * Ketu (South Lunar Node), shadow planet, spiritual karmic indicator.
@@ -4160,6 +4168,10 @@ export type KpChartResponse = {
4160
4168
  * KP sub-sub lord (SSL) of Ketu.
4161
4169
  */
4162
4170
  subSubLord: string;
4171
+ /**
4172
+ * KP number (1-249) locating Ketu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
4173
+ */
4174
+ kpNumber: number;
4163
4175
  };
4164
4176
  };
4165
4177
  /**
@@ -17477,7 +17489,7 @@ export type CalculateDrishtiResponses = {
17477
17489
  */
17478
17490
  200: {
17479
17491
  /**
17480
- * UTC datetime used for aspect calculation (ISO 8601).
17492
+ * Chart time the aspects were calculated for, echoed back as the local wall clock of the request (ISO 8601, no offset). This is the `date` and `time` you sent, NOT a UTC instant: hold them fixed and vary `timezone` and every longitude moves while this field does not. Combine it with the `timezone` you sent to recover the absolute moment.
17481
17493
  */
17482
17494
  datetime: string;
17483
17495
  /**
package/src/version.ts CHANGED
@@ -1,2 +1,2 @@
1
1
  // Generated by scripts/sync-version.ts. Do not edit.
2
- export const ROXY_UI_VERSION = '0.15.0';
2
+ export const ROXY_UI_VERSION = '0.15.1';