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.

Sign up for GitHub

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

Jump to bottom

Use microaeson from hackage instead of the fork #561

Closed
vrom911 opened this issue Feb 18, 2022 · 0 comments · Fixed by #562
Closed

Use microaeson from hackage instead of the fork #561

vrom911 opened this issue Feb 18, 2022 · 0 comments · Fixed by #562
Assignees
@vrom911
Milestone
v2.1: Modernize &...

Comments

@vrom911
Copy link
Member

vrom911 commented Feb 18, 2022

No description provided.

@vrom911 vrom911 self-assigned this Feb 18, 2022
vrom911 added a commit that referenced this issue Feb 18, 2022
@vrom911
[#561] Use microaeson from hackage instead of the fork
7710dc5 
Resolves #561
@vrom911 vrom911 mentioned this issue Feb 18, 2022
Merged
@chshersh chshersh added this to the v2.1: Modernize & Resurrect milestone Feb 18, 2022
chshersh pushed a commit that referenced this issue Feb 19, 2022
@vrom911
[#561] Use microaeson from hackage instead of the fork (#562)
1e1da21 
* [#561] Use microaeson from hackage instead of the fork

Resolves #561

* Update brick, fix stack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vrom911 vrom911

Labels
None yet
Projects
None yet
Milestone
v2.1: Modernize & Resurrect
Development

Successfully merging a pull request may close this issue.

[#561] Use microaeson from hackage instead of the fork kowainik/summoner
2 participants
@chshersh @vrom911