-
Notifications
You must be signed in to change notification settings - Fork 1
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
create new post screen #49
Conversation
Put a static maxLines for now, but this should depend on the available space.
The new post page is static for now, it will connect to the repository later.
Did this using Expanded. A problem is that the bottom part is now clickable. I don't know how to fix that. I tried using a spacer, but it does not mix well with the Expanded widget.
Only merge conflict was due to separation of login_page into 2 files in login package.
Nice work, this might require a small amount of UI code refactoring, similar to #37 (comment) and #38 (comment). |
Was using the mocked proxima page and navigating to new post page first, but this is not sustainable. These tests should only test the NewPostPage widget.
Text and hint content is now private, and keys are used for testing.
Thank you for the feedback, I did the refactoring to make the code more readable. I also changed the tests so that they only use this page and not the whole app to run. Please tell me if you find anything else that should be improved. |
onPressed: () { | ||
// TODO open tag and notification settings overlay | ||
}, | ||
icon: const Icon(Icons.settings), |
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 it would be a better idea to put the notification settings button in the top left of the screen (in a lot if app it's his default position).
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.
Good job!
The code is very clear and well structered. I added a UI design suggestion but you followed the wireframe so it's not to be addressed immediatly. I think we can go this way for now!
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, great refactoring.
No conflict except deleting the old home page file
Fixes #29,
This PR implements the new post screen.
The post button checks that the title and body are not empty. However it does not yet connect to the database, and there is therefore no viewmodel yet.
The settings button is not implemented yet. It will be implemented when user notifications and tag functionality will be implemented.