1import{_ as r,c as o,a as e,d as i,o as n}from"./app-CjUkjRdW.js";const s="/assets/fileviewprovider-lHKfUODW.png",l={};function a(d,t){return n(),o("div",null,t[0]||(t[0]=[e("h2",{id:"fileviewprovider",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#fileviewprovider"},[e("span",null,"FileViewProvider")])],-1),e("p",null,[i("There's one thing remaining to complete the picture: how does the IDE know which PSI tree to use for a given file? This is where the "),e("code",null,"FileViewProvider"),i(" comes in, with its "),e("code",null,"getPsi"),i(" method. It is a bridge between the PSI and the file system, and is responsible for creating the PSI tree for a given file.")],-1),e("p",{style:{"text-align":"center"}},[e("img",{src:s,alt:"FileViewProvider",width:"650"})],-1)]))}const c=r(l,[["render",a],["__file","99-tmp.html.vue"]]),p=JSON.parse(`{"path":"/nimjet/99-tmp.html","title":"","lang":"en-US","frontmatter":{},"headers":[{"level":2,"title":"FileViewProvider","slug":"fileviewprovider","link":"#fileviewprovider","children":[]}],"git":{"updatedTime":1725853500000},"filePathRelative":"nimjet/99-tmp.md","excerpt":"<h2>FileViewProvider</h2>\\n<p>There's one thing remaining to complete the picture: how does the IDE know which PSI tree\\nto use for a given file? This is where the <code>FileViewProvider</code> comes in, with its\\n<code>getPsi</code> method. It is a bridge between the PSI and the file system, and is responsible\\nfor creating the PSI tree for a given file.</p>"}`);export{c as comp,p as data};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.