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
Number string is converted to int #50
Comments
Seems like the code that is causing this is the regular expression in
Is there any way to prevent arcana from doing this? I could of course add a character in front of my value like |
Hi @brabanod 👋 It seems like you're the first person to request this type of behavior. Aside from the solution you proposed of adding an extra character, I see two other solutions that could be built into Arkana itself:
What do you think of these solutions? I lean towards less configurations (thus, less env vars), but not sure if the 2nd solution has any pitfalls I'm not seeing, that could potentially break people's code if they're using it 🤔 perhaps thinking of edge cases like massive numbers (larger than 64-bit) could break this unintentionally? What about negative numbers? I suppose these are already not supported anyway. Let me know what you think :) |
I opened a PR with the 2nd implementation above, and added extensive tests to cover the scenarios I could think of. Let me know if that works for you @brabanod 😃 |
Hey @rogerluan, sorry for the late response! |
Amazing, I'm glad it helped you! Thank you for your feedback @brabanod 🤗 really appreciate it! |
When I define a variable in my
.env
file like this:This will be translated by arkana into an integer with the trailing zeros being removed.
What I need however is to have the exact same string
"0001"
when I accessmyVar
in the code. Is this a bug or is there a way to force parsing as string?The text was updated successfully, but these errors were encountered: