Skip to content
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

Fix story printing when there are multiple periods #4939

Merged
merged 2 commits into from Apr 13, 2024

Conversation

carlobeltrame
Copy link
Member

Since the story overview UI only shows the story of one period at a time, we should also only print the story of that period when using the quick print feature.

Also, I fixed a wrong useAsyncData call in nuxt print. useAsyncData requires a string key as the first argument, and for all calls to useAsyncData with the same key, the same result data is returned. This led to nuxt print always printing the last period of the camp.

There are more wrong usages of useAsyncData in nuxt print, but I think we should fix these separately, in order not to block this supposedly small fix PR. I wasn't able to easily fix a connected issue in nuxt print that only happens locally: When using the print configurator to print a single activity, nuxt print outputs Error: props.scheduleEntry._meta is undefined.

@carlobeltrame carlobeltrame requested a review from usu April 13, 2024 15:02
@usu usu requested a review from manuelmeister April 13, 2024 16:40
Copy link
Member

@manuelmeister manuelmeister left a comment

Choose a reason for hiding this comment

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

Good by reading

@usu usu added this pull request to the merge queue Apr 13, 2024
Merged via the queue into ecamp:devel with commit e18b379 Apr 13, 2024
31 checks passed
@carlobeltrame carlobeltrame deleted the fix-story-printing-periods branch April 14, 2024 07:18
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.

None yet

3 participants