-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat(frontend): Page for Terms and Conditions #3116
feat(frontend): Page for Terms and Conditions #3116
Conversation
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 suggest to rename the route group (terms-and-conditions)
to (public)
.
The +layout
can maybe remain at the root of the group.
Ideally I would provide two PRs, one to initialize the public route, another for its content but fine if we keep it here.
src/frontend/src/lib/components/terms-and-conditions/TermsAndConditions.svelte
Outdated
Show resolved
Hide resolved
src/frontend/src/routes/(terms-and-conditions)/terms-and-conditions/+page.ts
Outdated
Show resolved
Hide resolved
@peterpeterparker you are right, new PR for the route: |
src/frontend/src/lib/components/terms-and-conditions/TermsAndConditions.svelte
Outdated
Show resolved
Hide resolved
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.
LGTm, thx
Motivation
We need a Terms and Condition page for OISY. The text was approved by Legal team. So, in this PR, we define the component to be used.
Screen.Recording.2024-10-25.at.11.11.12.mov