Support symbolic links
See original GitHub issueAt this time, the FileSystem
adapter explicitly ignores symbolic links when walking the source files:
Is there a reason for this behaviour? My build pipeline involves custom tooling built around broccolijs and uses symlinks to avoid copying files unnecessarily between various build steps - this change in @ui5/fs
breaks this for me.
Would you accept a PR that changes the hard-coded behaviour to allow symlinks? Or could this be configurable, and if so, how?
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Symlinks in Windows 10! - Windows Developer Blog
Symlinks, or symbolic links, are “virtual” files or folders which reference a physical file or folder located elsewhere, and are an important ...
Read more >The Complete Guide to Creating Symbolic Links (aka ...
Windows 11, 10, 8, 7, and Vista all support symbolic links — also known as symlinks — that point to a file or...
Read more >Symbolic Links - Win32 apps - Microsoft Learn
A symbolic link is a file-system object that points to another file system object. The object being pointed to is called the target....
Read more >How to Create Symbolic Links (Symlink) in Windows
Symlinks create references in other directories without copying files and folders over. Here's how to create symbolic links in Windows.
Read more >Create a symbolic link in Unix - IU KB - Indiana University
A symbolic link, also termed a soft link, is a special kind of file that points to another file, much like a shortcut...
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 Free
Top 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
Would be nice if you include this option into the ui5.yaml. I can‘t use any pipeline and always have to manually copy the webapp folder to geht rid of the symlinks and adapt the ui5 configuration to use the new folder.
Well, my pipeline hasn’t changed, but I’ve added a workaround step that makes a symlink-free copy of the project tree before handing that to the UI5 builder. It’s arguably ugly and overhead, but it works and doesn’t impact my daily development work.
I do still consider this at least a wart, but at this point it may as well be an issue of insufficient documentation than a bug.