Spec gotcha: directory entry must end with `/`
See original GitHub issueSourceItem
specifies that a directory entry must end with /
. This is a detail that is likely to be missed by implementors of the spec, both client and server and requires looking at the string to determine if something is a directory. I suggest making it an explicit field in SourceItem
(and probably DependencySourceItem
as well.
trait SourceItem {
/** Either a text document or a directory. A directory entry must end with a forward
* slash "/" and a directory entry implies that every nested text document within the
* directory belongs to this source item.
*/
def uri: Uri
/** Indicates if this source is automatically generated by the build and is not
* intended to be manually edited by the user. */
def generated: Boolean
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:24 (21 by maintainers)
Top Results From Across the Web
BSP 2.0 Milestone · GitHub
Spec gotcha: directory entry must end with / spec Involves a modification to the spec. #76 by jastice was closed on Feb 7,...
Read more >Gotchas - GitLab Docs
Assets that need to be served to the user are stored under the app/assets directory, which is later pre-compiled and placed in the...
Read more >CSCI 333 :: Storage Systems :: FUSE FAT
All file metadata is kept in the directory entry. At a minimum, this should include the file type (directory or file), the size...
Read more >CS137 FUSE Documentation
If you choose to use it, you should set that field in your open and opendir ... fi): Return one or more directory...
Read more >Administrivia NachOS–An Important Gotcha Fineprint for ...
NachOS–An Important Gotcha ... context switch time) complex –it should be in software ... Close: move the entry back to the directory.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds good, if you open a PR I’m happy to LGTM 👍
Solved via #83