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.

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

feat/fix: Allow to opt-out of replacing slashes in keys #116

Closed
wants to merge 2 commits into from

Conversation

BR0kEN-
Copy link

@BR0kEN- BR0kEN- commented Mar 30, 2023

@BR0kEN-
Copy link
Author

BR0kEN- commented Mar 30, 2023

@xiCO2k any idea how to fix that without introducing a BC?

@BR0kEN-
Copy link
Author

BR0kEN- commented Mar 31, 2023

Alright, the idea I have come up with to not bring a BC is to introduce the option that allows disabling the errorish (in some cases) behavior.

Covers my use case of the laravel-vue-i18n for 100% as I was never intent to use dot/slash notation.

@BR0kEN- BR0kEN- changed the title fix: Do not replace slashes in keys feat/fix: Allow to opt-out of replacing slashes in keys Mar 31, 2023
@xiCO2k
Copy link
Owner

xiCO2k commented Mar 31, 2023

Thanks for the PR, will review it and let you know

@BR0kEN-
Copy link
Author

BR0kEN- commented Apr 6, 2023

@xiCO2k please let me know whether this is something that can be expected or should I forget about it.

@xiCO2k
Copy link
Owner

xiCO2k commented Apr 8, 2023

Hey @BR0kEN- I think this is probably not the option.

I think a better way would be to take a look on both json with the full string and with the other way, do you want to make a PR with that?

Thanks again,
Francisco

@xiCO2k xiCO2k closed this Apr 8, 2023
@BR0kEN-
Copy link
Author

BR0kEN- commented Apr 9, 2023

Didn't get what you meant. What JSON?

@xiCO2k
Copy link
Owner

xiCO2k commented Apr 9, 2023

@BR0kEN- check the PR #118 if it looks good to you.

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.

2 participants