我有一个saveForm()函数,该函数有望按顺序执行以下操作:
下面是我的saveForm()函数:
saveForm() {
let fixedDepositEntity = this.getEntityFromForm();
this.fixedDepositsFirestoreCollection.add(fixedDepositEntity).then(documentRef => {
if (this.attachmentsFormArray.controls.length !== 0) {
this.attachmentsFormArray.controls.forEach(group => {
let fileRef = this.fireStorage.ref(this.fixedDepositsStorageFolderPath + group.get('fileName').value);
let uploadTask = fileRef.put(group.get('file').value);
// observe percentage changes
uploadTask.percentageChanges().subscribe(percent => {
group.get('percentComplete').setValue(Math.round(percent));
});
// get notified when the download URL is available
uploadTask.snapshotChanges().pipe(
finalize(() => {
fileRef.getDownloadURL().subscribe(url => {
group.get('downloadUrl').setValue(url);
});
}))
.subscribe();
});
}
});
}
当前,以上代码只是简单地循环访问附件表格数组,一旦文件被上传,最后便将downloadUrl分配给附件表格数组。
当用户选择多个文件时,我具有以下handleFileInput()事件处理程序:
handleFileInput(files: FileList) {
if (!files || files.length === 0) {
return;
}
Array.from(files).forEach(file => {
this.attachmentsFormArray.push(this.formBuilder.group({
fileName: [file.name],
fileSize: [file.size],
label: [''],
file: [file],
downloadUrl: [''],
percentComplete: [''],
uploadTaskState: ['']
}));
});
AngularFire库提供了snapshotChanges()方法,该方法返回Observable
我知道我们可以使用RxJs运算符来实现此行为,但是不确定在我的场景中使用哪个。如有任何帮助,我们将不胜感激。
编辑1:根据“ Mrk Sef's”答案实施。在大多数情况下,它都能正常工作。但是,有时不会设置downloadUrl。我无法理解此间歇性问题的原因。
saveForm() {
try {
this.fixedDepositsFormGroup.disable();
let fixedDepositEntity = this.getEntityFromForm();
this.fixedDepositsFirestoreCollection
.add(fixedDepositEntity)
.then(documentRef => {
this.isBusy = true;
// Changes will be mapped to an array of Observable, once this mapping
// is complete, we can subscribe and wait for them to finish
console.log('Voila! Form Submitted.');
if (this.attachmentsFormArray.controls.length !== 0) {
const changes = this.attachmentsFormArray.controls.map(
group => {
const fileRef = this.fireStorage.ref(this.fixedDepositsStorageFolderPath + group.get('fileName').value);
const uploadTask = fileRef.put(group.get('file').value);
const percentageChanges$ = uploadTask.percentageChanges().pipe(
tap(percent => group.get('percentComplete').setValue(Math.round(percent)))
);
const snapshotChanges$ = uploadTask.snapshotChanges().pipe(
finalize(() => fileRef.getDownloadURL().subscribe(url => group.get('downloadUrl').setValue(url)))
);
return [percentageChanges$, snapshotChanges$];
}
).reduce((acc, val) => acc.concat(val), []);; // Turn our array of tuples into an array
// forkJoin doesn't emit until all source Observables complete
forkJoin(changes).subscribe(_ => {
// By now all files have been uploaded to FireStorage
// Now we update the attachments property in our fixed-deposit document
const attachmentValues = (this.getControlValue('attachments') as any[])
.map(item => <Attachment>{
fileName: item.fileName,
fileSize: item.fileSize,
label: item.label,
downloadUrl: item.downloadUrl
});
documentRef.update({ attachments: attachmentValues });
console.log("Files Uploaded Successfully and Document Updated !");
});
}
})
.finally(() => {
this.fixedDepositsFormGroup.enable();
this.isBusy = false;
});
} finally {
}
}
答案 0 :(得分:1)
当第三方产生可观察的结果时,您会看到一个常见的设计,就是用一些您在通话时知道但订阅时可能不知道的自定义信息对其进行标记。
例如,获取标题以“ M”开头的每个文档的第三个单词:
const documents: Document[] = getDocumentsService();
wordStreams: Observable<[Document, HttpResponse]>[] = documents
.filter(file => file.title.charAt(0) === 'M')
.map(file => getThirdWordService(file.id).pipe(
map(serviceResponse => ([file, serviceResponse]))
);
merge(...wordStreams).subscribe(([file, serviceResponse]) => {
console.log(`The third word of ${file.title} is ${serviceResponse.value}`)
});
最大的收获是,通过将值映射到元组或对象(相同的模式处理对象,地图等),您可以通过流中的操作将这些信息向前传递。
唯一的问题是,如果您不小心,可能会得到不纯功能的流(可能对程序状态产生副作用)。
我不确定您的示例在做什么,但这是您想要的最好的猜测:
saveForm() {
let fixedDepositEntity = this.getEntityFromForm();
this.fixedDepositsFirestoreCollection
.add(fixedDepositEntity)
.then(documentRef => {
// Changes will be mapped to an array of Observable, once this mapping
// is complete, we can subscribe and wait for them to finish
const changes = this.attachmentsFormArray.controls.map(
group => {
const fileRef = this.fireStorage.ref(this.fixedDepositsStorageFolderPath + group.get('fileName').value);
const uploadTask = fileRef.put(group.get('file').value);
const percentageChanges$ = uploadTask.percentageChanges().pipe(
tap(percent => group.get('percentComplete').setValue(Math.round(percent)))
);
const snapshotChanges$ = uploadTask.snapshotChanges().pipe(
mergeMap(_ => fileRef.getDownloadURL()),
tap(url => group.get('downloadUrl').setValue(url))
);
return [percentageChanges$, snapshotChanges$];
}
).flat(); // Turn our array of tuples into an array
// forkJoin doesn't emit until all source Observables complete
forkJoin(changes).subscribe(_ =>
console.log("All changes are complete")
);
});
}
如果相反,您希望延迟将值写出直到订阅,这是另一种选择,该方法更清楚地标记了可观察流并添加了一些稍后使用的数据:
saveForm() {
let fixedDepositEntity = this.getEntityFromForm();
this.fixedDepositsFirestoreCollection
.add(fixedDepositEntity)
.then(documentRef => {
// Changes will be mapped to an array of Observable, once this mapping
// is complete, we can subscribe and wait for them to finish
const changes = this.attachmentsFormArray.controls.map(
group => {
const fileRef = this.fireStorage.ref(this.fixedDepositsStorageFolderPath + group.get('fileName').value);
const uploadTask = fileRef.put(group.get('file').value);
const percentageChanges$ = uploadTask.percentageChanges().pipe(
map(percent => ([group, percent]))
);
const snapshotChanges$ = uploadTask.snapshotChanges().pipe(
mergeMap(_ => fileRef.getDownloadURL()),
map(url => ([group, url]))
);
return [percentageChanges$, snapshotChanges$];
}
);
const percentageChanges$ = changes.map(([a, b]) => a);
const snapshotChanges$ = changes.map(([a, b]) => b);
merge(...percentageChanges$).subscribe({
next: ([group, percent]) => group.get('percentComplete').setValue(Math.round(percent)),
complete: _ => console.log("All percentageChanges complete")
});
merge(...snapshotChanges$).subscribe({
next: ([group, url]) => group.get('downloadUrl').setValue(url),
complete: _ => console.log("All snapshotChanges complete")
});
});
}
不言而喻,这些都没有经过测试。我希望您可以使用此处描述的内容来重新构建解决方案,以包括文件或您发现相关的任何其他信息。
我的解决方案创建了一个名为
的流const snapshotChanges$ = uploadTask.snapshotChanges().pipe(
mergeMap(_ => fileRef.getDownloadURL()),
tap(url => group.get('downloadUrl').setValue(url))
);
这并不是您真正想要的,您想要一个仅在uploadTask.snapshotChanges()完成后才开始的流。 Finalize很奇怪,因为它可以对失败和完成进行操作,我确定可以配置一个运算符来执行此操作,但是我不知道该怎么做。
我的解决方案创建了一个自定义运算符(waitForEnd
),该自定义运算符在源代码完成或出错时会发出布尔值,并忽略源流中的所有其他元素
const waitForEnd = () =>
waitOn$ => new Observable(obsv => {
const final = (bool) => {
obsv.next(bool);
obsv.complete();
}
waitOn$.subscribe({
next: _ => {/*do nothing*/},
complete: () => final(true),
error: _ => final(false)
});
return {unsubscribe: () => waitOn$.unsubscribe()}
});
let snapshotChanges$ = uploadTask.snapshotChanges().pipe(
waitForEnd(),
mergeMap(_ => fileRef.getDownloadURL()),
tap(url => group.get('downloadUrl').setValue(url))
);
snapshotChanges$
将等待uploadTask.snapshotChanges()
结束,然后才会获得下载URL并在完成之前设置值。