Skip to content

Add Data 2030 Summit for data #7768

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 3 commits into from
Jul 10, 2025
Merged

Add Data 2030 Summit for data #7768

merged 3 commits into from
Jul 10, 2025

Conversation

confs-tech-bot
Copy link
Collaborator

Conference information

Website: https://data2030summit.com

// data

{
  "name": "Data 2030 Summit",
  "url": "https://data2030summit.com",
  "startDate": "2025-10-21",
  "endDate": "2025-10-22",
  "city": "Stockholm",
  "country": "Sweden",
  "online": true,
  "locales": "EN"
}

@confs-tech-bot confs-tech-bot requested a review from cgrail as a code owner June 13, 2025 13:17
@@ -685,6 +685,16 @@
"bluesky": "infoq.bsky.social",
"mastodon": "@infoq@techhub.social"
},
{
"name": "Data 2030 Summit",
"url": "https://data2030summit.com",

Choose a reason for hiding this comment

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

[url] If a year is present in the URL, it should match the event start or end year

@JuanPabloDiaz
Copy link
Collaborator

the URL and conference name are correct. Data 2030. previous conference #6889

// file checkConference.ts
            // Check if the year in the URL matches the event start or end year
            assertField(year === eventStartYear || year === eventEndYear, property, `If a year is present in the URL, it should match the event start or end year`, value);
        }

@JuanPabloDiaz
Copy link
Collaborator

@cgrail, Do you prefer a different approach to handle this specific case?

@JuanPabloDiaz
Copy link
Collaborator

@cgrail, Do you prefer a different approach to handle this specific case?

With this modification, URL validations will be skipped for conferences where the year in the URL is part of the conference's name.

For example:

  • If a conference is called "Data 2030 Summit" and its URL is "https://data2030summit.com/", the validation will be skipped because "2030" appears in both the name and the URL.
  • If a conference is called "Cloud 2040 Conference" and its URL is "https://cloud2040conference.com/", the validation will also be skipped.

This will prevent false positives in cases where the year in the URL isn't actually a reference to the event year, but rather part of the conference's brand name.


However, this could allow URLs that should actually be validated. For example, if a conference is called "DevCon 2025" but its URL is "https://devcon2024.com/", the validation will be skipped even though the year in the URL (2024) doesn't match the event year (2025).

@JuanPabloDiaz JuanPabloDiaz requested a review from nimzco July 10, 2025 17:14
Copy link
Member

@nimzco nimzco left a comment

Choose a reason for hiding this comment

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

Looks good to me! Good idea :)

@JuanPabloDiaz JuanPabloDiaz merged commit 9ecc451 into main Jul 10, 2025
2 checks passed
@JuanPabloDiaz JuanPabloDiaz deleted the fgwvjadazchvoggiwrl branch July 10, 2025 23:03
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