Closed jrson83 closed 1 year ago
@jrson83 Thank you for your attention. As you can see, sparkee use conventional-changelog internal to generate CHANGELOG.md, but as my usage experience, conventional-changelog is hard to use because API and document, now I have plan to implement a new tools for changelog, the purpose is to have better performance and a more flexible API.
@Geocld did you already start working on this? I really would like to use sparkee for a monorepo in production, but this issue is holding me back. If you didn't start yet I could create a temporary PR?
@jrson83 Still working on it,but not finish yet, really look forward to seeing your input. Thanks for your contribution.
@Geocld I didn't work much with streams before, but I got it working after some hours. I gonna do the PR after some optimization and a cleanup tomorrow.
Is it okay for you when I first introduce a PR to improve typings
? I really like this project and would like to contribute in order to optimize and reduce usage of third party deps size to make it even better!
@jrson83 No problem! you can contribute and optimize what you can do,let us make this project better! thank you!
@Geocld Sorry, I was busy this week. I will complete the PR soon. Did you work with rome before? It has very lightweight dependencies (24MiB) and is much faster then prettier and eslint. We could migrate from them to rome.
@jrson83 I've heard of rome
but haven't used it yet,this is a good idea to use rome to improve quality of sparkee code, I will try it in next version!
@Geocld awesome. I have setup rome for sparkee already. I will create another PR, you can check if all is good before merging :ok_hand:
Cool, I will check it out today.
@Geocld Thank you :grin: The new CHANGELOG is awesome! Keep up the good work. I will close this issue.
I want to make some more improvements and will open a new issue for a new improvement you can comment on.
Summary of the feature being proposed
Add two capabilities:
# Changelog
to the top ofCHANGELOG.md
(following two line breaks)append
toprepend
(or add an option to useprepend
orappend
)prepend
is enabled and the fileCHANGELOG.md
exists, check if the first line is# Changelog\n\n
and prepend the new release between heading and last releaseWhat value does this feature bring?
The
CHANGELOG.md
should have the headingChangelog
as this is expected.When using a changelog generator, the expected behaviour is, the new release gets prepended to the top of
CHANGELOG.md
, instead of beeing appended to the bottom.EDIT: The heading could also be an userOption
header
, like stated in conventional-changelog-config-spec.Are you willing to implement this feature yourself?
Yes, just let me known!