📱 Client Type
Other
💻 Operating System
macOS
📦 Deployment Platform
No response
📌 Version
v2.2.17
🌐 Browser
Other, Chrome
🐛 What happened?
Since v2.2.17+, file-derived documents are not visible under the Pages category. The documentArm condition ne(d.sourceType, 'file') and buildFileCategoryFilter returning 'none' for Pages are mutually exclusive, which produces an empty result set.
Impact
Users cannot see file-derived documents under the Pages category. The category appears empty, which makes file-derived pages effectively inaccessible through this filter path.
📷 How to reproduce it?
Use a build affected by v2.2.17+.
Navigate to or select the Pages category.
Look for file-derived documents.
Observe that no file-derived documents are displayed
Category filter: Pages
documentArm / file category filter
🚦 What it should be?
Root Cause
The issue appears to be caused by two conflicting filters:
js
ne(d.sourceType, 'file')
This excludes file-sourced documents from the document arm.
js
buildFileCategoryFilter(category) // Pages => 'none'
For the Pages category, the filter evaluates to 'none', which further filters out the file/document arm.
Because one filter excludes sourceType === 'file' and the other prevents the files arm from passing anything for Pages, the combined result is an empty set.
Suggested Fix
When category === 'Pages', exempt the sourceType exclusion, or let the files arm allow custom / document when the category is Pages.
Example direction:
ts
const shouldExcludeFile = category !== 'Pages' && ne(d.sourceType, 'file');
or:
ts
if (category === 'Pages') {
// do not apply the sourceType exclusion
// or allow custom/document in the files arm
}
📝 Additional Information
Root Cause
The issue appears to be caused by two conflicting filters:
js
ne(d.sourceType, 'file')
This excludes file-sourced documents from the document arm.
js
buildFileCategoryFilter(category) // Pages => 'none'
For the Pages category, the filter evaluates to 'none', which further filters out the file/document arm.
Because one filter excludes sourceType === 'file' and the other prevents the files arm from passing anything for Pages, the combined result is an empty set.
Suggested Fix
When category === 'Pages', exempt the sourceType exclusion, or let the files arm allow custom / document when the category is Pages.
Example direction:
ts
const shouldExcludeFile = category !== 'Pages' && ne(d.sourceType, 'file');
or:
ts
if (category === 'Pages') {
// do not apply the sourceType exclusion
// or allow custom/document in the files arm
}
🛠️ Willing to Submit a PR?
None
✅ Validations
📱 Client Type
Other
💻 Operating System
macOS
📦 Deployment Platform
No response
📌 Version
v2.2.17
🌐 Browser
Other, Chrome
🐛 What happened?
Since v2.2.17+, file-derived documents are not visible under the Pages category. The documentArm condition ne(d.sourceType, 'file') and buildFileCategoryFilter returning 'none' for Pages are mutually exclusive, which produces an empty result set.
Impact
Users cannot see file-derived documents under the Pages category. The category appears empty, which makes file-derived pages effectively inaccessible through this filter path.
📷 How to reproduce it?
Use a build affected by v2.2.17+.
Navigate to or select the Pages category.
Look for file-derived documents.
Observe that no file-derived documents are displayed
Category filter: Pages
documentArm / file category filter
🚦 What it should be?
Root Cause
The issue appears to be caused by two conflicting filters:
js
ne(d.sourceType, 'file')
This excludes file-sourced documents from the document arm.
js
buildFileCategoryFilter(category) // Pages => 'none'
For the Pages category, the filter evaluates to 'none', which further filters out the file/document arm.
Because one filter excludes sourceType === 'file' and the other prevents the files arm from passing anything for Pages, the combined result is an empty set.
Suggested Fix
When category === 'Pages', exempt the sourceType exclusion, or let the files arm allow custom / document when the category is Pages.
Example direction:
ts
const shouldExcludeFile = category !== 'Pages' && ne(d.sourceType, 'file');
or:
ts
if (category === 'Pages') {
// do not apply the sourceType exclusion
// or allow custom/document in the files arm
}
📝 Additional Information
Root Cause
The issue appears to be caused by two conflicting filters:
js
ne(d.sourceType, 'file')
This excludes file-sourced documents from the document arm.
js
buildFileCategoryFilter(category) // Pages => 'none'
For the Pages category, the filter evaluates to 'none', which further filters out the file/document arm.
Because one filter excludes sourceType === 'file' and the other prevents the files arm from passing anything for Pages, the combined result is an empty set.
Suggested Fix
When category === 'Pages', exempt the sourceType exclusion, or let the files arm allow custom / document when the category is Pages.
Example direction:
ts
const shouldExcludeFile = category !== 'Pages' && ne(d.sourceType, 'file');
or:
ts
if (category === 'Pages') {
// do not apply the sourceType exclusion
// or allow custom/document in the files arm
}
🛠️ Willing to Submit a PR?
None
✅ Validations