8000 JSON Module Support for Elixir 1.18 and CI Environment Updates by michelboaventura · Pull Request #264 · akoutmos/prom_ex · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

JSON Module Support for Elixir 1.18 and CI Environment Updates #264

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

michelboaventura
Copy link

This PR introduces conditional JSON handling and updates our CI environment:

  • Adds a new PromEx.JSON module that automatically uses Elixir 1.18's built-in JSON module when available, falling back to Jason otherwise
  • Makes the Jason dependency optional
  • Adds Elixir 1.18 to the testing matrix
  • Updates actions/cache action to v4

Change description

What problem does this solve?

Issue number: (if applicable)

Example usage

Additional details and screenshots

Checklist

  • I have added unit tests to cover my changes.
  • I have added documentation to cover my changes.
  • My changes have passed unit tests and have been tested E2E in an example project.

 This PR introduces conditional JSON handling and updates our CI environment:

* Adds a new PromEx.JSON module that automatically uses Elixir 1.18's built-in JSON module when available, falling back to Jason otherwise
* Makes the Jason dependency optional
* Adds Elixir 1.18 to the testing matrix
* Updates `actions/cache` action to v4
@michelboaventura
Copy link
Author

hey @akoutmos do you think this approach is a good one for we to start using JSON on the lib? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0