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

fix: priority always rejected + cleanup form validation #11

Merged
merged 17 commits into from
Apr 23, 2024
Merged

fix: priority always rejected + cleanup form validation #11

merged 17 commits into from
Apr 23, 2024

Conversation

iMarbot
Copy link
Contributor

@iMarbot iMarbot commented Apr 19, 2024

As reported by @hjpalpha on discord, the form data is rejected by the php because it is returned as string rather than as int/number type. This should check string for being all digits (int-like) and then convert to int before sending off to update db.

If there's a better way to fix this, feel free to change or close this PR.

Added a small change to i18n for submit buttons too.

@iMarbot iMarbot requested a review from godarkrai April 19, 2024 12:13
@iMarbot iMarbot changed the title fix: form rejected due to string/int type differences on priority fix: priority always rejected + minor cleanup Apr 20, 2024
@iMarbot iMarbot requested a review from FO-nTTaX April 20, 2024 14:27
@iMarbot iMarbot changed the title fix: priority always rejected + minor cleanup fix: priority always rejected + cleanup form validation Apr 21, 2024
@iMarbot
Copy link
Contributor Author

iMarbot commented Apr 22, 2024

I pushed your changes on my dev here http://darkrai.wiki.tldev.eu/rocketleague/Special:ResourceLoaderArticles feel free to test if you want.

@godarkrai I tested it and it all appears to work as desired.

@godarkrai
Copy link
Member

LGTM

@FO-nTTaX FO-nTTaX merged commit 830876e into Liquipedia:master Apr 23, 2024
2 checks passed
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.

3 participants