Gleipnir/nidus-sync
2
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Establish basic pattern for compliance data flow

Browse source 
We can get location, images, and string data. It's the trifecta.
This commit is contained in:
Eli Ribble 2026-04-09 17:35:00 +00:00
parent 8d6976c770
commit a6912929a7
No known key found for this signature in database
3 changed files with 81 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

6
ts/rmo/content/compliance/Address.vue
View file

@ -26,8 +26,8 @@
<script setup lang="ts">
import { ref } from "vue";
import type { District } from "@/type/api";
import { router } from "@/rmo/router";
import type { District } from "@/type/api";
import HeaderCompliance from "@/rmo/components/HeaderCompliance.vue";
import ProgressBarCompliance from "@/rmo/components/ProgressBarCompliance.vue";
import AddressAndMapLocator from "@/rmo/components/AddressAndMapLocator.vue";
@ -44,6 +44,8 @@ const props = defineProps<Props>();
const locator = ref<Locator | null>(null);
function doContinue() {
emit("doLocator", locator.value);
router.push("./concern");
// re-add when we have the concern data to show
// router.push("./concern");
router.push("./evidence");
}
</script>