feat: main bounty form #110
Merged
Conversation
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
- Added a new button to open a drawer for creating a new bounty. - Introduced a form for bounty creation with fields for type, title, description, and amount. - Updated the changeset to include new fields and validation logic for the bounty form. - Enhanced the navigation module to manage the state of the bounty form visibility.
- Implemented a default handle_event function returning {:noreply, socket} in several LiveView modules to manage events without specific handlers.
- Updated the bounty form in the dashboard to include a new radio button selection for bounty type, enhancing user interaction.
- Refined the layout of the bounty form for improved usability and responsiveness.
- Added a new function to provide type options for the bounty form, allowing users to select between "GitHub issue" and "Custom". - Refactored the form layout to dynamically render radio buttons for type selection, improving user interaction. - Updated the changeset validation to ensure the selected type is part of the defined options. - Introduced data attributes for better handling of form visibility based on the selected type.
- Changed the `bounty_form` function to use a more generic `form` assign, improving consistency across the form's implementation. - Updated the form's HTML structure to reflect the new assign, enhancing clarity and maintainability. - Adjusted the import of `Tails` for class helpers to improve organization within the `AlgoraWeb` module. - Added a new event handler for `create_bounty_main` to manage form submission events effectively.
- Changed the warning message for existing bounties to improve clarity and user experience across multiple LiveView modules. - Ensured consistency in messaging by standardizing the text in `home_live.ex`, `swift_bounties_live.ex`, and `dashboard_live.ex` files.
- Updated the bounty form validation to require only the title for custom types, enhancing clarity in user input requirements. - Simplified the HTML structure for the form by removing unnecessary string conversions, improving readability. - Refactored event handling methods to unify the naming convention, ensuring consistency across the LiveView modules. - Initialized the bounty form with a default type of "github" to improve user experience during form creation.
- Added a new `create_bounty` function to handle the creation of bounties with associated ticket details and options for visibility and sharing. - Introduced a `notify_bounty` function to alert about bounty notifications, enhancing the notification system. - Updated the `Ticket` schema with a new changeset function for better validation of ticket parameters. - Refactored the `Nav` module to support dynamic bounty creation based on selected types, improving user experience.
- Modified the `notify_bounty` function to return `{:ok, nil}` instead of `{:ok, Oban.Job.t()}`, simplifying the return type.
- Updated the `Ticket` changeset to require only the `:title`, making the `:url` field optional.
- Added a migration to make the `url` field in the `tickets` table nullable, enhancing flexibility in ticket creation.
- Refactored the `Nav` module to improve redirection logic after bounty creation based on type, enhancing user experience.
- Introduced a `host` assignment in both `BountyLive` and `OG.BountyLive` modules to streamline access to user data associated with the bounty's ticket repository. - Updated ticket reference handling to conditionally assign values based on the presence of a repository, improving robustness. - Adjusted the rendering logic to utilize the new `host` assignment for displaying user information and avatar, enhancing code clarity and maintainability.
- Removed commented-out code in the bounty form to enhance readability and maintainability. - Streamlined the `handle_event` function in the `Nav` module by eliminating unnecessary checks and improving the flow of bounty creation logic. - Ensured that the changeset handling is more concise, enhancing clarity in the event processing for bounty creation.
- Added a `can_create_bounty?` function in the `Member` module to determine if a user can create bounties based on their role. - Updated the `GithubController` to utilize the new function for authorization checks when creating bounties. - Refactored the `BountyLive`, `DashboardLive`, and `Nav` modules to conditionally render UI elements based on the user's ability to create bounties, enhancing user experience and code clarity.
- Updated the ordering of bounties in the `BountyLive` module to prioritize the current organization, enhancing the relevance of displayed bounties. - Removed a TODO comment regarding pooling bounties for better code clarity.
- Simplified the `input` function in `CoreComponents` by removing unnecessary debugging code. - Enhanced the `RepoNav` module by introducing a conditional `main_bounty_form` assignment based on user permissions, improving clarity and maintainability. - Refactored event handling for bounty creation, ensuring better error handling and user feedback during the process.
- Removed redundant radio button options for bounty form type, streamlining the user interface. - Consolidated input fields for bounty details, improving layout and accessibility. - Updated the share drawer component to maintain functionality while enhancing code clarity.
zcesur
added a commit
that referenced
this pull request
Apr 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.