-
Notifications
You must be signed in to change notification settings - Fork 83
Village long description #1863
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
base: main
Are you sure you want to change the base?
Village long description #1863
Conversation
us-east-1 detected |
wlcx
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is partially a draft PR, sorry if you already had any of these on your list!
- Looks like the migration needs "rebasing" onto the newest HEAD migration.
- My humble request would be for new code to have type annotations. Very happy to help if there's any mypy gnarliness.
- From a UX perspective I think we should state the markdown limitations (i.e. images disabled) in the form.
I'll leave the security considerations to someone with more experience in that area 😅
| <a href="{{ village.map_link }}">📍 Map</a> | ||
| {% endif %} | ||
|
|
||
| {# TODO: Can we show what's on at the village venues here? #} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going to say that I'm not sure whether there's a link between Venue and Village, but on closer look Venue has a village_id field :)
@SamLR is this planned to still be the case?
ad00281 to
8b17a7b
Compare
8b17a7b to
3ad70e8
Compare
There is still a lot to tidy up here but wanted to get some opinions sooner rather than later about iFrame layout options
Add a long_description field to villages. This is markdown from untrusted users and is rendered using nh3 and a sandboxed iFrame in order to limit the untrusted HTML.
There are 2 layout options for the iFrame:
The first uses javascript to resize the iFrame to prevent scrolling within the iFrame.
The second uses a static size for the iFrame which scrolls for long content.
The advantage of the second is that we can remove the allow-scripts privilege from the iFrame.
fixes #1816