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

V1.9.1 is completely broken #171

Open
SanderSander opened this issue Aug 26, 2022 · 8 comments
Open

V1.9.1 is completely broken #171

SanderSander opened this issue Aug 26, 2022 · 8 comments
Labels

Comments

@SanderSander
Copy link

SanderSander commented Aug 26, 2022

This commit broke a lot:

9e570ee

When the default directory is used: The following error is triggered because of a missing DIRECTORY_SEPERATOR

[Exception]
/workspaceresources/lang doesn't exists!

Also i'm sure version 4 of laravel doesn't work because the $langs variable is overwriten, and therefor it also misses the /

@Chomiciak
Copy link

@SanderSander just a while ago I've created a comment addressing the problem #170 (comment)

The problem is disappearing slash /.
The version should be removed as soon as possible.

@rmariuzzo
Copy link
Owner

I apologize, will try to remove the version ASAP. 😞

@SanderSander
Copy link
Author

SanderSander commented Aug 26, 2022

#172 I made a PR that fixes the problem

@rmariuzzo
Copy link
Owner

I removed the broken version from Packagist, I think that should help for now: https://packagist.org/packages/mariuzzo/laravel-js-localization

@rmariuzzo
Copy link
Owner

#172 I made a PR that fixes the problem

I review your PR, looks fine to me. @SanderSander and @Chomiciak can you check the PR too? 🙇

@rmariuzzo rmariuzzo added the bug label Aug 26, 2022
@Chomiciak
Copy link

@rmariuzzo
Thank you very much for your fast response :)

I suppose you should give the version a different tag on packagist, to ensure people re-download this patched version.

Over all, this is a feature addition, so shouldn't it be updated on the 2nd digit (1.10/1.10.0), not the 3rd (1.9.1)? Generally most packages reserve 3rd digit for patches.

@SanderSander
Copy link
Author

SanderSander commented Aug 26, 2022

@rmariuzzo Thank you very much for your fast response :)

I suppose you should give the version a different tag on packagist, to ensure people re-download this patched version.

Over all, this is a feature addition, so shouldn't it be updated on the 2nd digit (1.10/1.10.0), not the 3rd (1.9.1)? Generally most packages reserve 3rd digit for patches.

I made the same suggestion for versioning in the PR :)

@rmariuzzo
Copy link
Owner

Thank you both for your good advices. I appreciate it.

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

No branches or pull requests

3 participants