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

Inline-ify the clashing function #1279

Merged
merged 1 commit into from
Sep 2, 2020
Merged

Inline-ify the clashing function #1279

merged 1 commit into from
Sep 2, 2020

Conversation

harimohanraj89
Copy link
Contributor

Story card: https://app.clubhouse.io/simpledotorg/story/1128/broken-tablesort

On investigation, it appears that the initializeTables function that was being used to initialize tablesort is now clashing with an initializeTables method in reports.js.

This PR simply inlines the initialization of tablesort to avoid naming clashes, but it's a good reminder that we need to start writing properly scoped JS 😄

@harimohanraj89 harimohanraj89 temporarily deployed to simple-review-pr-1279 September 2, 2020 09:22 Inactive
@harimohanraj89 harimohanraj89 merged commit ff93255 into master Sep 2, 2020
@harimohanraj89 harimohanraj89 deleted the fix-tablesort branch September 2, 2020 09:31
harimohanraj89 pushed a commit that referenced this pull request Sep 3, 2020
…1285)

The second git tag here will always fail, because we have already
created the tag as an annotated tag. This causes the script to bail out with an error:

```
[~/src/simpledotorg/simple-server (master)]> bin/release
CHANGELOG
---------
• Lower the explain threshold for New Relic to 0.25 (#1284)
• Add index to rx drugs (#1283)
• Allow Admins to Edit accesses (#1252)
• Migrate the Admin::UsersController and its actions (#1280)
• Index "twilio_sms_delivery_details.session_id" (#1277)
• Inline-ify the clashing function (#1279)
• More efficient strategy for inviting new admins (#1263)
• More efficient tree for displaying access resources (#1262)
• Permissions: flesh out roles and actions (#1208)
Creating release release-2020-09-02-1. Continue? (y/N):
y
fatal: tag 'release-2020-09-02-1' already exists
```

I'm also adding the #releases channel to the final help message.
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.

None yet

2 participants