You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{% for y in range (info.current_year, 1993, -1) %}
Realistically, this is an inherent issue with the design of the year nav dropdown. This problem will only get worse as more and more years pass (as we will have more and more years to include), and we're already excluding 1993. Though, I'm unsure if that is intended or if the author of the above code was unaware of range's end-exclusivity, as AFAIS 1993 is the last year with a decent cluster of accounts associated with it.
As stated, the real issue is that overtime this list will just get larger and larger. It would be optimal to implement a different method for year selection. There are many solutions that could be used. Bootstrap has a range input selector that could be placed in the dropdown paired with a submit button to effectively do the same thing, or there could just be a text input box as well.
This is tangentially related to #19 , but I think having the year selection in the navbar on every page is a useful feature. As it currently stands, I find an advanced search to be somewhat unnecessary (though, it would certainly be a net positive if properly implemented).
The text was updated successfully, but these errors were encountered:
Due to:
profiles/profiles/templates/include/nav.html
Line 26 in d37a116
Realistically, this is an inherent issue with the design of the year nav dropdown. This problem will only get worse as more and more years pass (as we will have more and more years to include), and we're already excluding 1993. Though, I'm unsure if that is intended or if the author of the above code was unaware of range's end-exclusivity, as AFAIS 1993 is the last year with a decent cluster of accounts associated with it.
As stated, the real issue is that overtime this list will just get larger and larger. It would be optimal to implement a different method for year selection. There are many solutions that could be used. Bootstrap has a range input selector that could be placed in the dropdown paired with a submit button to effectively do the same thing, or there could just be a text input box as well.
This is tangentially related to #19 , but I think having the year selection in the navbar on every page is a useful feature. As it currently stands, I find an advanced search to be somewhat unnecessary (though, it would certainly be a net positive if properly implemented).
The text was updated successfully, but these errors were encountered: