saksenasonali opened a new pull request, #771: URL: https://github.com/apache/atlas/pull/771
What changes were proposed in this pull request? Align dashboard validation and API payloads with Atlas TimeBoundary so users may set only a start or end bound, with clearable date fields and submit-time checks. AddValidityPeriod.tsx Removed required validation on start/end time fields. Start and end pickers no longer default to “now” when empty; they show blank (null). Added isClearable on both date pickers so either bound can be cleared. “Add Validity Period” initializes rows with startTime, endTime, and timeZone as null (replacing invalid validityPeriod: ""). AddTag.tsx On submit, each validity period must have at least one of start or end time; otherwise show a warning toast and abort. When both are set, end must be after start (toast + abort if not). Build API validityPeriods with only valid bounds (UTC YYYY/MM/DD HH:mm:ss); omit unset startTime/endTime instead of sending invalid dates. Timezone remains required per row (unchanged). Motivation: Atlas server TimeBoundary and AtlasClassificationType allow start-only or end-only periods; the UI previously required both and always sent both fields. How was this patch tested? Automated cd dashboard && npm run lint — pass (0 errors; existing repo warnings only). cd dashboard && npm run build — pass (tsc, Vite production build, atlas-lineage prebuild). mvn -pl intg -Dtest=TestAtlasClassificationType test with -Datlas.surefire.options="--add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED" — 47 tests, 0 failures (covers valid/invalid TimeBoundary cases including start-only and end-only). Validation doc: https://cloudera.atlassian.net/wiki/spaces/~712020724c468d4b1b49c5b265ad4a4a0b3a6f/pages/12370477067/Validation+Atlas+React+UI+Classification+Validity+Period+optional+start+or+end -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
