dotenv-rs / dotenv

Library to help supply environment variables in testing and development

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Current maintenance state

zamazan4ik opened this issue · comments

Hi!

I see that for a long time there is no activity in this repo. Is the library still maintained? If not maybe will be a good idea to share access rights to the repo with some volunteers and keep this crate maintained.

Thanks in advance!

Related issue: #60

CC @ZoeyR

commented

It would be nice if someone looked at #72 to fix the IDE/Rust Analyzer error

unresolved macro proc_macro_call!

I have written @ZoeyR a mail a few weeks ago, though I have not received any response. I would love to help out though

It looks like up to 11 people have fixes/improvements ready:
https://github.com/dotenv-rs/dotenv/network

I also wrote an email to @ZoeyR, today,
and an other one to all the authors mentioned in Cargo.toml

commented

I've created a fork called dotenvy. It's published to crates.io as:

  1. dotenvy
  2. dotenvy_codegen
  3. dotenvy_codegen_impl

I've merged in many of the PRs from this repo.

This fork is intended to serve as the development home for the dotenv implementation in Rust.

Legend has it that the Lost Maintainer will return, merging changes from dotenvy into dotenv with such thrust that all Cargo.tomls will lose one keystroke. Only then shall the Rust dotenv crateverse be united in true harmony.

Until then, this repo dutifully carries on the dotenv torch. It will be actively maintained. Contributions and PRs are very welcome!

[0.15.1] - 2022-02-28

Added

  • dotenv crate forked as dotenvy
  • dotenv_codegen forked as dotenvy_codgen
  • dotenv_codegen_implementation forked as dotenvy_codegen_impl
  • Crate description for dotenvy_codegen
  • Crate description for dotenvy_codgen_impl
  • New language in README
  • MIT license badge in README
  • Generate helpful errors from dotenv! macro (full merge of dotenv-rs/dotenv #58)

Changed

Removed

  • example folder. The simple example has been moved to the README.
  • extern
  • unnecessary use statements in doc examples

ehh wow, cool @allan2 , thank you! :-)
would you be interested/willing in additional maintainers (e.g. @somehowchris)? not that it's necessary .. I am happy with there being an active fork already.. thanks for mentioning it here!

ouh and .. maybe also mention it in all the PRs in this repo which you already merged, to flock more crowd over to your fork.

I did that now. :-)
@allan2, Did you already add @somehowchris as backup maintainer on your repo?

commented

Thanks for the support @hoijui.
I'm definitely willing to add more maintainers. I don't think there's a need right now though.

If the fork picks up, I'll open a Discussion on the new repo to ask who's interested!