Skip to content
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

Support work with existing project #8

Open
vrom911 opened this issue Aug 22, 2017 · 3 comments
Open

Support work with existing project #8

vrom911 opened this issue Aug 22, 2017 · 3 comments
Assignees
Labels
CLI Command line interface interaction feature generated project Files, folder generation by the summoner
Milestone

Comments

@vrom911
Copy link
Member

vrom911 commented Aug 22, 2017

Add update command which can upgrade current project with missing features.

@vrom911 vrom911 added CLI Command line interface interaction generated project Files, folder generation by the summoner labels Sep 23, 2017
@vrom911 vrom911 added this to the v1.1 Upgrade milestone May 30, 2018
@chshersh
Copy link
Contributor

chshersh commented Jun 14, 2018

I will enumerate here what we can add to existing projects. Only simple staff that we can do without depending on Cabal library:

  • Add .travis.yml
    • cabal or not
    • ghc versions
    • paths to stack.yaml with GHC versions
  • Add Appveyor CI config
    • Has stack?
  • Add executable stanza
    • Name of the package
    • Library or not
    • GHC version
    • default-extensions
    • custom prelude
  • Add test stanza
    • Name of the package
    • GHC version
    • default-extensions
    • custom prelude
  • Add doctest
  • Add bench stanza
    • Name of the package
    • Library or not
    • GHC version
    • default-extensions
    • custom prelude
  • Add library stanza
    • Name of the package
    • GHC version
    • default-extensions
    • custom prelude
  • Add stack.yaml for specified GHC version
    • Ghc version
  • Add .gitignore (rewrite existing one with our all-inclusive .gitignore)
  • Change LICENSE to new one (with warning to update license in .cabal file)
    • Name of the license
    • Author name
  • Add CHANGELOG (with warning to update extra-doc-files in .cabal file)
    • Name of the package (same as repo)
    • Owner
    • Github or not
  • Add README.md (with badges)
    • Name of the package (repo)
    • stack or not
    • travis or not
    • appveyor or not
    • description

For some commands we need project name and GitHub owner name. Project name can be extracted from .cabal file. GitHub name we can ask for now if it's not specified in global configuration.

Also in some commands we need to add badges to README file in addition to creating new files. We can just put them in the beginning.

@carliros
Copy link

This is a nice feature!
any news on this?

@vrom911
Copy link
Member Author

vrom911 commented Apr 10, 2019

@carliros Thanks for your interest!

We just released 1.3.0 version yesterday with some other new features included. We will try to create the Milestone for the following release soon and will include a realistic amount of new features in there.

We will keep you updated under this issue 🙂

@chshersh chshersh added this to the v2.0: Major update milestone Jun 1, 2019
@chshersh chshersh removed this from the v2.0: Major update milestone Feb 22, 2020
@chshersh chshersh pinned this issue May 6, 2020
@chshersh chshersh added this to the v2.1: Update milestone Jul 12, 2020
@chshersh chshersh removed this from the v2.1: Update milestone Sep 18, 2021
@chshersh chshersh added this to the v3.0: Update milestone Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI Command line interface interaction feature generated project Files, folder generation by the summoner
Projects
No open projects
Development

No branches or pull requests

3 participants