Skip to content
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

Es1 4 final steps #198

Open
wants to merge 31 commits into
base: develop
Choose a base branch
from

Conversation

MisakaZentai
Copy link

@MisakaZentai MisakaZentai commented Dec 9, 2024

Description

I implement the final step pages.

Related Issue

If this PR addresses an issue, link to it here.

Type of Change

Please select the type(s) of change that apply and delete those that do not.

  • Bug fix: A non-breaking change that fixes an issue.
  • New feature: A non-breaking change that adds functionality.
  • Breaking change: A change that causes existing functionality to not work as expected.
  • Documentation update: Changes or updates to documentation.
  • Code style update: Changes that do not affect the meaning of the code (e.g., formatting).
  • Refactoring: A code change that neither fixes a bug nor adds a feature.
  • Performance improvement: A change that improves performance.
  • Test enhancement: Adding or updating tests; no production code change.
  • Chore: Changes to the build process or auxiliary tools; no production code change.
  • Other: (please describe)

Proposed Solution

Describe your code changes in detail. Explain how you implemented your solution and any design decisions you made.

How to Test

Provide instructions on how to test these changes. Include details on test configurations, test cases, and expected outcomes.

Unit Tests

List the unit tests added or modified to verify your changes.

Documentation Updates

Indicate whether documentation needs to be updated due to this PR.

  • Yes
  • No

If yes, describe what documentation updates are needed and link to the relevant documentation.

Checklist

  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • Any dependent changes have been merged and published in downstream modules.

Additional Information

Add any other information that might be useful for the reviewers.

mickey4653 and others added 30 commits June 26, 2024 11:24
	- created env file for config
	- updated firebase rules
	- and updated the firebase project name
	- fixed Eslint errors
	- Created a component template and Design Quick Action Button
	- implemented efficiency state management. (ES2.4)
	- implemented user feedback using loading state. (ES2.4)
	- added more quick action buttons
	- fixed Eslint Errors
	- Added Other Quick Action buttons
	- Updated Eslint Fix Errors
	- changle color styling using theme palette
	- Removed Close icon
	- added padding between quick action button text and icon
	- added styling for other quick action buttons
	- added disabled state
	- made text for quick action buttons dynamic
	- added default buttion for quick action
	- fixed Eslint Errors
	- fixing pop up quick action buttons responsiveness
	- made buttons dynamic passed through text
	- fixed Eslint errors
	- Created Discover Library branch
	- Fixed Eslint Errors
	- Created a Page for discovery Library
	- added discoveryLibrary UI template in chat template directory
	- Design and integrated Discovery Library UI
	- Fixed Eslint Errors
	- added images to custom prompts
	- Fixed ESlint errors
	- added discover librari UI template
	- made chat template reusable into hooks
	- removed background on cards
	- got changes from surbhi (discovery button)
	- routed discovery button to discovery library ui page
	- added user dynamic state when user logs in
	- made sure discovery button is centered correctly
	- added route to discovery library ui
	- fixed eslint formatting
	- Created OnBoarding Component for welcome page
	- created page to route to welcome page
	- addded some styling for welcome page design
	- fixed Eslint Errors
	- imported image dropdown icon
	- created routes to profile setup
	- created and designed progress bar component
	- made progress bar resusable props in welcome screen component
	- recreated progress bar component due to bug issue
	- Refactored the code for progress bar component
	- removed unnecessary stylings on welcome component
Copy link

@poojithreddy28 poojithreddy28 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MisakaZentai,

What issue is this Pull Request actually resolves. Can you update the pull request with all the details filled within PR template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants