Move JavaScript function to its own file #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Iain-S
force-pushed
the
mv-js-to-own-file
branch
from
4cb1a53
to
24640d2
Compare
Iain-S
force-pushed
the
mv-js-to-own-file
branch
from
5353eb1
to
4517d0b
Compare
Iain-S
commented
Nov 16, 2023
Iain-S
force-pushed
the
mv-js-to-own-file
branch
from
95b0d0b
to
0105254
Compare
Iain-S
force-pushed
the
mv-js-to-own-file
branch
from
0105254
to
2b2ec16
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move some JavaScript to its own .js file. This makes it easier to get syntax highlighting and easier to lint the JS.
See https://eslint.org/docs/latest/ for a thorough description of all rules.
Refactor how the details page RBAC list is sorted so that it isn't O(n*m).