Skip to content

Make columns sortable#289

Draft
octonato wants to merge 1 commit into
javaconferences:mainfrom
octonato:sorting-columns
Draft

Make columns sortable#289
octonato wants to merge 1 commit into
javaconferences:mainfrom
octonato:sorting-columns

Conversation

@octonato
Copy link
Copy Markdown

Makes the columns sortable so we can easily see which CFPs deadlines are approaching.

It's a kind of a hack, because the dates are free text. Sorting it requires some regex parsing and such. It works, but it's kind of ugly.

This relates to #208. If we were using a fixed date format, we won't need any regex.

Comment thread site.generator.java
<body>""" +
patchedBody +
" <script>\n" +
" window.addEventListener('DOMContentLoaded', function () {\n" +
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

this function moved into site.js.

Having the javascript in its own file make it easier to read it and evolve it. And then we can just inject the whole file when generating.

@rmannibucau
Copy link
Copy Markdown
Collaborator

What about enforcing the format (supporting date and ranges) at build time? Then sorting is trivial. Think it was the first impl and is a must to be reliable

@octonato
Copy link
Copy Markdown
Author

@rmannibucau, I agree, but there is another issue about this (#208). It doesn't seem there is a consensus yet though.

I'm fine to drop this PR or re-work it after there is a decision about #208.

@octonato
Copy link
Copy Markdown
Author

octonato commented May 18, 2026

@rmannibucau, I agree, but there is another issue about this (#208). It doesn't seem there is a consensus yet though.

I'm fine to drop this PR or re-work it after there is a decision about #208.

Sorry for the noise. I see now that you have been commenting and is aware of #208.

Anyway, the thing is, this PR just get the sorting in place using the existing text format. No doubt a structured format is better if you want to sort, but I didn't want to solve #208 and add sorting in a single PR. Also because there is not decision about #208.

@rmannibucau
Copy link
Copy Markdown
Collaborator

my 2cts is that it is trivial to support MM-yy dd-MM-yyyy yyyy-MM-dd and iso format (by checking length and iphen positions) but yes I think #208 can be worth solving before this one since it does simplify a lot the automotion and potentially how we can make the site getting an API (potentially post processing raw data to generate a proper json) so in terms of "roadmap" (if it makes sens there) I would do it this way instead of going with hacks which bite later on

indeed just my 2 cts, not a blocking comment at all

@alina-yur
Copy link
Copy Markdown
Collaborator

Thank you for your contribution, @octonato!

My 2c. I have two user flows for this repo:
— check the CFP date for a specific conference (scroll chronologically or Cmd+F for the name);
— check what is currently open (Cmd+F for "open", also the green emojis).

So for me the current format works.

It doesn't seem like we reached any consensus on #208.

@noctarius @bmvermeer @HanSolo do you have opinions on whether we need sorting?

@jonatan-ivanov
Copy link
Copy Markdown
Contributor

There are a few options in #208 (comment). I think the best would be separating start and end dates and using ISO 8601 to format them but this is also the one that needs the most effort.

@octonato octonato marked this pull request as draft May 18, 2026 20:29
@octonato
Copy link
Copy Markdown
Author

I put his PR in draft. Since it's a bloody hack, we should just wait for #208 to land in one or other form. Then we can revisit this one.

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.

4 participants