Commit Graph

104 Commits

Author SHA1 Message Date
8a28a5dd0f
HPath.IO.Errors: fix throwDestinationInSource
'canonicalizePath' was missing, making this function far less reliable.
In order for this to work we have to work around circular imports
with a IO.hs-boot file.
2016-05-10 00:11:42 +02:00
78a3baeb25
Export PathException 2016-05-09 19:34:19 +02:00
a3b1528974
Raise cabal version to fix travis build 2016-05-09 19:15:18 +02:00
7aac9bcb93
Adjust description 2016-05-09 19:06:31 +02:00
930b021a32
Add missing (<$>) imports 2016-05-09 18:53:26 +02:00
6b6c7f05c9
Try to fix travis build 2016-05-09 18:39:13 +02:00
a83e96259f
Fix build with bytestring >= 0.10.8 2016-05-09 18:17:33 +02:00
14b48515a2
Add TODO to _copyFile 2016-05-09 18:15:05 +02:00
820bf8814d
Fix build with GHC versions prior 7.10.x 2016-05-09 18:14:08 +02:00
e18d2dd2d6
Remove ghc versions that don't have PatternSynonyms 2016-05-09 18:13:34 +02:00
117b3dc7d7
Add travis icon to README 2016-05-09 18:06:40 +02:00
c0ceccf716
Add travis build 2016-05-09 18:04:28 +02:00
010756e190
Fix cabal file 2016-05-09 18:03:27 +02:00
9a4fd00710
Release 0.5.9 2016-05-09 17:37:33 +02:00
f27becc4df
Cleanup, improve docs 2016-05-09 17:37:16 +02:00
3bbde22377
Add 'hiddenFile' to System.Posix.FilePath 2016-05-09 17:37:00 +02:00
3da8533b48
Remove 'normalize' from HPath, since it's not needed 2016-05-09 17:04:26 +02:00
687a113252
Fix documentation in System.Posix.FilePath 2016-05-09 17:04:01 +02:00
86a4b9ade2
Add IO modules, previously from HSFM 2016-05-09 16:53:31 +02:00
6638cd8cc1
Create HPath.IO module, adding canonicalizePath again 2016-05-09 14:40:30 +02:00
4ce35b9bec
TESTS: minor doctest cleanup 2016-05-09 14:17:12 +02:00
196647a383
Move some functionality from HPath to System.Posix.FilePath
This also removes 'canonicalizePath' from HPath which fixes
the doctest.
2016-05-09 14:16:53 +02:00
cfe626b6d4
Update README 2016-05-09 13:37:21 +02:00
a946387330
Merge posix-paths into hpath 2016-05-09 13:31:20 +02:00
1263fac7ec
Update submodule 2016-05-02 19:10:40 +02:00
45b515d1db
Add withAbsPath/withRelPath/withFnPath 2016-04-17 18:09:50 +02:00
a5360f29a3
Don't re-export functions 2016-04-16 19:21:19 +02:00
f1875da780
Use latest posix-paths
Pending upstream PR.
2016-04-16 19:12:23 +02:00
7e8c745e35
Clean up, rewrite stuff 2016-04-16 18:17:44 +02:00
577ecf6750
Add normalizeAbs, which may or may not be useful 2016-04-15 14:23:25 +02:00
8f7e5806e3
Be more strict
* don't rely on OverloadedString
* make basename fail if run on root dir "/"
* reject "." and ".." in filename parser
* reject ".." in path parsers
* normalise paths in parsers
2016-04-15 14:23:07 +02:00
c570505297
Add hiddenFile function 2016-04-10 21:50:52 +02:00
148eeb619f
Implement String -> ByteString and vice versa conversion for filepaths 2016-04-05 00:55:25 +02:00
877d8c4089
Implement equalFilePath 2016-04-05 00:54:55 +02:00
8c1bd139c0
Readd TH constructors 2016-04-05 00:54:36 +02:00
bd71947b2a
Use word8 package 2016-04-04 18:46:25 +02:00
491efe44a3
Use ByteString for paths instead of String 2016-04-04 17:29:35 +02:00
hasufell
c7229061d0 Fix encoding issues with realPath 2016-04-04 03:06:22 +02:00
3a52a9ea4b
Add getAllParents 2016-04-03 16:20:38 +02:00
3c3a2d2766
Switch to new layout 2016-03-30 02:47:42 +02:00
d15e4b8ad9 Fork chrisdone's path library
I wasn't happy with the way it dealt with Dir vs File things. In his
version of the library, a `Path b Dir` always ends with a trailing
path separator and `Path b File` never ends with a trailing path separator.

IMO, it is nonsensical to make a Dir vs File distinction on path level,
although it first seems nice.
Some of the reasons are:
* a path is just that: a path. It is completely disconnected from IO level
  and even if a `Dir`/`File` type theoretically allows us to say "this path
  ought to point to a file", there is literally zero guarantee that it will
  hold true at runtime. So this basically gives a false feeling of a
  type-safe file distinction.
* it's imprecise about Dir vs File distinction, which makes it even worse,
  because a directory is also a file (just not a regular file). Add symlinks
  to that and the confusion is complete.
* it makes the API oddly complicated for use cases where we basically don't
  care (yet) whether something turns out to be a directory or not

Still, it comes also with a few perks:
* it simplifies some functions, because they now have guarantees whether a
  path ends in a trailing path separator or not
* it may be safer for interaction with other library functions, which behave
  differently depending on a trailing path separator (like probably shelly)

Not limited to, but also in order to fix my remarks without breaking any
benefits, I did:
* rename the `Dir`/`File` types to `TPS`/`NoTPS`, so it's clear we are only
  giving information about trailing path separators and not actual file
  types we don't know about yet
* add a `MaybeTPS` type, which does not mess with trailing path separators
  and also gives no guarantees about them... then added `toNoTPS` and
  `toTPS` to allow type-safe conversion
* make some functions accept more general types, so we don't unnecessarily
  force paths with trailing separators for `(</>)` for example... instead
  these functions now examine the paths to still have correct behavior.
  This is really minor overhead. You might say now "but then I can append
  filepath to filepath". Well, as I said... we don't know whether it's a
  "filepath" at all.
* merge `filename` and `dirname` into `basename` and make `parent` be
  `dirname`, so the function names match the name of the POSIX ones,
  which do (almost) the same...
* fix a bug in `basename` (formerly `dirname`) which broke the type
  guarantees
* add a pattern synonym for easier pattern matching without exporting
  the internal Path constructor
2016-03-08 22:53:42 +01:00
Chris Done
e2974d3152 Bump to 0.5.7 2016-03-06 17:43:49 +01:00
Chris Done
dbee82c69b Merge pull request #14 from felixonmars/patch-1
Fix a haddock parse error
2016-03-06 17:43:02 +01:00
Felix Yan
05271c94af Fix a haddock parse error
The line was triggering parse error when running haddock:

```
src/Path.hs:16:1:
    parse error on input ‘-- | A normalizing well-typed path type.’
```

Removing it works for me.
2016-03-05 13:44:08 +08:00
Chris Done
9d357b24c8 Remove redundant check for /= . or .. 2016-03-04 15:11:06 +01:00
Chris Done
62c681819c Update test suite 2016-03-04 15:09:21 +01:00
Chris Done
c41fa86d17 Bump to 0.5.6 2016-03-04 15:07:00 +01:00
Chris Done
04608e0e53 Reject only .. and . (#13) 2016-03-04 15:06:27 +01:00
Chris Done
47450b5dd6 Bump to 0.5.5 2016-03-04 14:50:28 +01:00
Chris Done
540c24f3a5 Use FilePath.isValid (#12) 2016-03-04 14:49:21 +01:00