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

Issue 181 fix some mod searching #491

Merged
merged 3 commits into from
Dec 9, 2014

Conversation

Martii
Copy link
Member

@Martii Martii commented Dec 8, 2014

See commit summaries for specifics.

@jerone and @Zren ... how about this?

jerone and others added 2 commits December 7, 2014 18:48
* Apparently flagged true form variable is carried over between tabs/refreshes so remove it when not on a flagged query
* Resolve incremental form variable by moving `isFlagged` into conditional
* Stray trailing comma in object fix
* Remove some dead code
* Some STYLEGUIDE.md conformance with missing braces and newlines, and some strict equality test *(still one left in this file but not testing there yet)*
* Tested non-flagged routes and checks okay

Closes OpenUserJS#181
@Martii Martii added CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. PR READY This is used to indicate that a pull request (PR) is ready for evaluation. bug You've guessed it... this means a bug is reported. labels Dec 8, 2014
@Zren
Copy link
Contributor

Zren commented Dec 8, 2014

This is the bug right here: https://github.com/OpenUserJs/OpenUserJS.org/blob/master/libs/modelQuery.js#L180

We're reusing the same array for every request. We need to copy (probably deepcopy) the default arrays instead of reusing it.

@Martii
Copy link
Member Author

Martii commented Dec 9, 2014

We're reusing the same array for every request.

Correct and you answered your line note question with this. Because I'm still newer to this portion of code it would be useful to have some pointers on where to do a deep copy (clone the initial array) and bring that cloned variable into an isolated and non-reused scope... that would be a refactor not a fix like this PR is. Because time is limited for spending on this issue (just as jerone alluded to when he deassigned himself) with assisting it would keep it in within the time frame that I've allotted. I do have other duties as usual and I'm more inclined to get this patch deployed in the next few hours with any luck and mitigate a new issue with a refactor... See #492

Martii added a commit that referenced this pull request Dec 9, 2014
Issue 181 fix some mod searching

Auto-merge ... confirmation of theory versus test results... this is a fix and generating a new refactor issue.
@Martii Martii merged commit 09b509c into OpenUserJS:master Dec 9, 2014
@Martii Martii deleted the Issue-181FixSomeModSearching branch December 9, 2014 00:32
@Martii Martii removed the PR READY This is used to indicate that a pull request (PR) is ready for evaluation. label Dec 9, 2014
Martii pushed a commit to Martii/OpenUserJS.org that referenced this pull request Dec 9, 2014
* Very odd boog... dev had `Search Flagged Libraries` and pro had `Search Libraries` until I blanked out dev lib flags... then they matched. Force the text in along with the flag just to be sure. DOM duplication now appears to be related only to the logic issue at OpenUserJS#492

Post fix for OpenUserJS#491
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug You've guessed it... this means a bug is reported. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment.
Development

Successfully merging this pull request may close these issues.

3 participants