generated from SoftStackFactory/group-project-frontend-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/admin create event #40
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
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
3468bb3
login and register created
rita7elyz 52a4d72
login and register created
rita7elyz f670394
merge origin/dev
rita7elyz 24d5e29
Merge branch 'dev' of https://github.com/SoftStackFactory/my-request-…
rita7elyz e0d9362
stepper added with form field for event name
rita7elyz 21c70ce
added create event and manage event, slider working, tabs working
rita7elyz c2f7ea9
added second slider
rita7elyz 5a1e809
added styling to sliders and stepper buttons
rita7elyz 78ce548
content page started, hard coded image
rita7elyz d78e712
added styling to images and began setting up drag and drop feature
rita7elyz 98d1688
drag and drop implemented
rita7elyz 0df23c5
removed dummy register and login components
rita7elyz d9cdeb3
compiling and login and register removed
rita7elyz 7176c68
adjusted dragdrop feature
rita7elyz fe05a17
add
rita7elyz 0ab2bc8
started implementing two list drag and drop
rita7elyz a1b98bf
still getting splice error on drag and drop
rita7elyz 5d683ce
drag and drop working
rita7elyz 1bea99e
final commit
rita7elyz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think I've settled on a preference for: new/campaign, manage/campaign
I think that is clean and understandable
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.
gotcha, i've updated it. Since I was able to use the tabs, this path might be better named something more general since it includes both create and manage functionalities. path: 'campaigns' Thoughts?
Uh oh!
There was an error while loading. Please reload this page.
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.
Not a bad Idea. I like the idea of having the 2 routes available for us. In the future we can use them to decide which tab we start on when the component loads. So, if a link form another part of the site goes to manage/campaign then it will go to the same component but start on the manage tab.
I see you are changing it in the other PR, so it will be fine here for now.