serokell/xrefcheck
1
1
Fork 0
mirror of https://github.com/serokell/xrefcheck.git synced 2024-09-11 13:37:36 +03:00
Code Issues Projects Releases Wiki Activity
f08e24c734
xrefcheck/stack.yaml

20 lines
509 B
YAML
Raw Normal View History

[#36] Switch to lts-15.13 Problem: LTS-14.16 that we currently using and a bit old. And its GHC is old as well. Solution: update the resolver, make some changes that were necessary. They are pretty trivial. The only essential breaking change is the removal of `parseUrl` from `req`.
2020-05-19 21:17:58 +03:00
# SPDX-FileCopyrightText: 2018-2020 Serokell <https://serokell.io>
[INT-128] Make the repository REUSE compliant Problem: nowadays we want all files to store licensing information in machine-readable format and to use reuse tool to check that. But the repo is not REUSE compliant. Solution: add `LICENSES` folder and licensing information for each file.
2019-12-18 17:18:55 +03:00
#
# SPDX-License-Identifier: MPL-2.0
[OPS-1023] CI: pin hackage.nix and stackage.nix independently
2020-08-10 15:08:07 +03:00
# To update hackage and stackage indexes used by CI run:
# $ niv update hackage.nix; niv update stackage.nix
[#107] Update stack resolver to the newer version Problem: We had old resolver version, that used ghc 8.10.4 and outdated versions of libraries Solution: Change resolver to lts 19.13, that uses ghc 9.0.2 and update haskell.nix configuration files to can build project via `nix-build` command
2022-07-06 16:54:23 +03:00
resolver: lts-19.13
[INT-31] Implement cross-references verifier
2018-10-11 00:15:08 +03:00
packages:
- .
extra-deps:
[#81] Add config option for protected links Problem: We do not know what to do with protected links, because we cannot check them. So we have two options, assume that these links is valid or not. Solution: Provide config option for user to decide what to do - assume protected links valid or not.
2021-08-04 12:05:38 +03:00
- firefly-0.2.1.0@sha256:e9d73486464c3e223ec457e02b30ddd5b550fdbf6292b268c64581e2b07d888b,1519
[Chore] Pull cmark-gfm 0.2.5 from hackage Problem: in #158, we started using `optFootnotes` from the `cmark-gfm` package. This feature hadn't yet been released on hackage, so we pulled the package from its github repo. Since then, cmark-gfm-0.2.5 has been released on hackage. Solution: pull the latest version from hackage and add a lower bound on the dependency.
2022-10-07 23:09:35 +03:00
- cmark-gfm-0.2.5
[#201] Use nyan-interpolation for building error messages Problem: We often need to create large strings, and we use different fmt tools for this (by-hand concatenation, unlinesF, etc). Sometimes it is unclear or too heavy, and it always can be called error-prone Solution: use `int` quasiquoter to build large strings and have nice-looking and easy-to-read code
2022-10-25 21:37:28 +03:00
- git: https://github.com/serokell/nyan-interpolation
[#164] Use only '/' as path separator Problem: in markdown links, '/' should always be used as path separator , e.g. GitHub renderer is not threating link `[x](a\b.md)` as a link to file in dir `a` We use OS-dependent file separators everywhere, so e.g. `canonizeLocalRef "./a.md"="./a.md`"` on Windows Solution: replace '\' to '/' while constructing repo tree if needed and then use only '/', preferring functions from `System.FilePath.Posix`. We can do this, since 'a/b' and `a\b` are equivalent paths on Windows
2022-10-11 23:35:44 +03:00
commit: 348355385466d6d0116251b463a2842ecce0360d
[#201] Use nyan-interpolation for building error messages Problem: We often need to create large strings, and we use different fmt tools for this (by-hand concatenation, unlinesF, etc). Sometimes it is unclear or too heavy, and it always can be called error-prone Solution: use `int` quasiquoter to build large strings and have nice-looking and easy-to-read code
2022-10-25 21:37:28 +03:00
subdirs:
- full
- core
Reference in New Issue Copy Permalink