You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The everything server's resource indexing is counterintuitive. While the array index starts at 0, the resource numbering in URIs starts at 1, which leads to confusing behavior where:
Resource at index 0 is accessed via URI "test://static/resource/1"
Resource at index 1 is accessed via URI "test://static/resource/2"
etc.
From the server code:
constALL_RESOURCES: Resource[]=Array.from({length: 100},(_,i)=>({
const url=`test://static/resource/${i+1}`;if(i%2===0){// index 0 (first resource) is text// index 2 (third resource) is text// etc.
This means even-indexed resources (0,2,4...) are text, but they map to odd-numbered URIs (1,3,5...).
To Reproduce
Make a ListResources request, then try to read the first text resource:
Describe the bug
The everything server's resource indexing is counterintuitive. While the array index starts at 0, the resource numbering in URIs starts at 1, which leads to confusing behavior where:
etc.
From the server code:
This means even-indexed resources (0,2,4...) are text, but they map to odd-numbered URIs (1,3,5...).
To Reproduce
Make a ListResources request, then try to read the first text resource:
Expected behavior
Either:
The text was updated successfully, but these errors were encountered: