-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve OSS metadata, refactor #381
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no place for me here... I will choose the truth I like.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job!
@@ -1,3 +1 @@ | |||
packages: summoner-cli/ summoner-tui/ | |||
|
|||
tests: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did they fix the behaviour?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, they didn't. I actually deleted these lines accidentally, sorry for that...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries!
summoner-cli/src/Summoner.hs
Outdated
import Summoner.Default as Summoner | ||
import Summoner.GhcVer as Summoner | ||
import Summoner.License as Summoner | ||
import Summoner.Project as Summoner | ||
import Summoner.Question as Summoner | ||
import Summoner.Settings as Summoner | ||
-- QUESION: Conflicting imports with Tree (File); should we rename something? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! I would say that we need better name for Source
as I don't have an immediate answer on what it means - source-file, is it the raw file or is it a link? But on the other hand, it would be used in TOML, so we should be careful with the renaming that...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I had the same idea. Maybe we can call it Copy
? We already removed Link
constructor, so it's kinda okay to rename one more constructor... Also, I don't think that File
is used that often, so it should be okay to rename it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or Local?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went for Local
, I like it a lot 👍
SPDX-License-Identifier: MPL-2.0 | ||
Maintainer: Kowainik <xrom.xkov@gmail.com> | ||
|
||
This module contains functions for stack template creation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I guess this is outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it seems so 🙂 This line is so 2017....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
@@ -73,6 +73,7 @@ The changelog is available [on GitHub][2]. | |||
want. | |||
* [#327](https://github.com/kowainik/summoner/issues/327): | |||
Better AppVeyor CI configuration for both `cabal` and `stack`. | |||
* Rename `file` confing file of `source` to `local`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add Breaking change
here?
No description provided.