-
Notifications
You must be signed in to change notification settings - Fork 24
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
Frontend related features [1] #1596
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1596 +/- ##
===========================================
- Coverage 42.90% 42.87% -0.03%
===========================================
Files 328 328
Lines 10041 10048 +7
===========================================
Hits 4308 4308
- Misses 5733 5740 +7
*This pull request uses carry forward flags. Click here to find out more.
|
[WJ-1179] Add svelte component for page view
[WJ-1155] First basic UI interaction to edit a page
Will have to merge these changes to dev for now and continue working off of the new changes in dev |
For |
Probably yes, or in |
Sounds good, thanks. If it's not possible we should create a custom directory for frontend for assets. (Maybe symbolic links would work?) |
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.
Left a lot of comments, but mostly fine to go. You can change these in a follow-up PR to maintain momentum.
let options: string[] = [] | ||
if (data.options.noRender) options.push("norender") | ||
options = options.map((opt) => `/${opt}`) | ||
goto(`/${data.page.slug}${options.join("")}/edit`, { |
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.
Maybe we should expose a method of converting options back into a URL path.
This tracks the Jira issues and features for frontend I am trying to tackle.
Done: