fix: update tsbuildinfo and refine component rendering
- Updated tsconfig.tsbuildinfo to include additional components, ensuring proper TypeScript build configuration. - Refined rendering logic in ContentRow.vue to simplify the v-for directive for better readability. - Removed unused variables and functions in ZapModal.vue, streamlining the code and improving maintainability. These changes enhance the build process and improve code clarity across components.
This commit is contained in:
@@ -53,7 +53,7 @@
|
||||
>
|
||||
<span class="flex -space-x-1.5">
|
||||
<img
|
||||
v-for="(pk, i) in getZapperPubkeys(content.id).slice(0, 3)"
|
||||
v-for="pk in getZapperPubkeys(content.id).slice(0, 3)"
|
||||
:key="pk"
|
||||
:src="zapperAvatarUrl(pk)"
|
||||
:alt="''"
|
||||
|
||||
@@ -250,8 +250,6 @@ const zapInvoiceId = ref<string | null>(null)
|
||||
|
||||
// LNURL fallback (only used when backend zap not available)
|
||||
const lnurlCallback = ref<string | null>(null)
|
||||
const lnurlMinSats = ref(1)
|
||||
const lnurlMaxSats = ref(10_000_000)
|
||||
const verifyUrl = ref<string | null>(null)
|
||||
|
||||
// Invoice data
|
||||
@@ -398,30 +396,6 @@ function startPollingBackend() {
|
||||
}, 3000)
|
||||
}
|
||||
|
||||
/**
|
||||
* Poll the LNURL verify URL to detect payment (direct Lightning-address flow).
|
||||
* Only used when backend zap is not used.
|
||||
*/
|
||||
function startPolling() {
|
||||
if (!verifyUrl.value) return
|
||||
|
||||
const url = verifyUrl.value
|
||||
pollInterval = setInterval(async () => {
|
||||
try {
|
||||
const response = await fetch(url)
|
||||
if (!response.ok) return
|
||||
|
||||
const data = await response.json()
|
||||
if (data.settled === true || data.preimage) {
|
||||
cleanup()
|
||||
showSuccess()
|
||||
}
|
||||
} catch {
|
||||
// Silently retry
|
||||
}
|
||||
}, 3000)
|
||||
}
|
||||
|
||||
function showSuccess() {
|
||||
successQuote.value = successQuotes[Math.floor(Math.random() * successQuotes.length)]
|
||||
paymentState.value = 'success'
|
||||
|
||||
Reference in New Issue
Block a user