Skip to content

Update What's New modal for 2025.4: maps, bulk entity delete, etc.#1434

Merged
ktuite merged 3 commits intomasterfrom
ktuite/whats_new_2025_4
Dec 9, 2025
Merged

Update What's New modal for 2025.4: maps, bulk entity delete, etc.#1434
ktuite merged 3 commits intomasterfrom
ktuite/whats_new_2025_4

Conversation

@ktuite
Copy link
Member

@ktuite ktuite commented Dec 6, 2025

Closes getodk/central#1487

Screenshot 2025-12-05 at 2 09 20 PM

What has been done to verify that this works as intended?

Why is this the best possible solution? Were any other approaches considered?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Does this change require updates to user documentation? If so, please file an issue here and include the link below.

Before submitting this PR, please make sure you have:

  • run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@ktuite ktuite force-pushed the ktuite/whats_new_2025_4 branch 2 times, most recently from 419a0a9 to 657b707 Compare December 6, 2025 02:32
@ktuite ktuite changed the title What's new modal for 2025.4 Update What's New modal for 2025.4: maps, bulk entity delete, etc. Dec 6, 2025
@ktuite
Copy link
Member Author

ktuite commented Dec 6, 2025

Still need to

  • re-add eslint ignore alt text
  • resize images -- they've been compressed but they are much larger than they need to be

@ktuite ktuite force-pushed the ktuite/whats_new_2025_4 branch from 657b707 to a30b27a Compare December 8, 2025 22:02
@ktuite ktuite force-pushed the ktuite/whats_new_2025_4 branch from a30b27a to 2d8b925 Compare December 8, 2025 22:04
@@ -1,3 +1,4 @@
<!-- eslint-disable vuejs-accessibility/alt-text -->
Copy link
Member

Choose a reason for hiding this comment

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

I think it'd be a little better to put this right above the first <template>. We do that in a few other cases. That way the copyright, etc. can continue to start on the first line.

Comment on lines -122 to -123
<!-- Autogenerated by destructure.js -->
<i18n>
Copy link
Member

Choose a reason for hiding this comment

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

You don't need to delete this manually, it will be modified automatically when translations are updated.

// When updating `canUpdateForm` in the future, consider the *verb* for the audience.
// For 2025.4, we decided it could be shown to project viewers as well,
// where the previous modal was only shown to admins and project managers.
const canUpdateForm = currentUser.can('form.update') ||
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
const canUpdateForm = currentUser.can('form.update') ||
const canUpdateForm = currentUser.can('submission.list') ||

I think the two verbs on this line and the next should be consistent.

@ktuite ktuite force-pushed the ktuite/whats_new_2025_4 branch from cc4d7bc to 7d5ba0e Compare December 8, 2025 22:56
@ktuite ktuite merged commit 590c98a into master Dec 9, 2025
5 of 9 checks passed
@ktuite
Copy link
Member Author

ktuite commented Dec 9, 2025

I am planning to come back and fix the e2e test in a new PR by modifying the test to update the user preference ahead of time to dismiss the modal.

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.

Update What's New modal for v2025.4

2 participants