Skip to content

dashboard cleanup #394

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

Merged
merged 1 commit into from
Aug 3, 2020
Merged

dashboard cleanup #394

merged 1 commit into from
Aug 3, 2020

Conversation

scrittler
Copy link
Contributor

  • move URI to left column for easier visual identification
  • move cfc name to content panel
  • ensure URI sorting is case-insensitive

* move URI to left column for easier visual identification
* move cfc name to content panel
* ensure URI sorting is case-insensitive
Copy link
Owner

@atuttle atuttle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has my blessing.

@@ -852,7 +852,7 @@
<cffunction name="sortURIMatchOrder" access="private" output="false">
<cfargument name="endpoints" />
<cfset var URIMatchOrder = listToArray( structKeyList(arguments.endpoints, chr(10)), chr(10) ) />
<cfset arraySort(URIMatchOrder, "text", "desc") />
<cfset arraySort(URIMatchOrder, "textnocase", "desc") />
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line change gave me quite a bit of pause. I was worried that we might lose some nuance of the way we handle incoming URI's and some tiny corner case bug might be introduced by moving from more explicit to less...

But then I realized that we're using these strings as patterns in a reMatchNoCase() so it was already case insensitive.

<cfset local.attempt = reMatchNoCase(application._taffy.URIMatchOrder[local.i], arguments.requestedURI) />

I am still mildly curious what problem this solves. The only thing I can think of is carelessness from developers in using consistent casing that might result in separation of resources in the dashboard that might have otherwise been grouped:

For example, using a case-sensitive sort:

/Users/abb
/users/bbb
/users/aaa

Whereas a case-insensitive sort would result in:

/users/bbb
/Users/abb
/users/aaa

@atuttle atuttle merged commit 1e63923 into atuttle:master Aug 3, 2020
@dklmuc dklmuc mentioned this pull request Aug 16, 2020
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