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

Feature/captioning calculator #1

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ghughes13
Copy link

Feature: CC-XXXX

Notes: Adds functioning caption calculator for clients to get a rough idea of how many captioning minutes they'd need. **First time using tailwind and remix so please be forgiving with any dumb mistakes I've made related to that. Deployed to Netlify if you'd like to see a live demo. There's still a lot of refactoring/polish I'd do if this was going to production, but it's at a prototype quality level. Happy to hop on a call and go over anything in more detail if you'd like.

Demo: https://feature-captioning-calculator--startling-shortbread-4eadcc.netlify.app/

Desktop Image:
Desktop

Mobile Image:
mobile

Copy link
Member

@raytiley raytiley left a comment

Choose a reason for hiding this comment

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

@ghughes13 - Nice job. Just some follow questions and one minor nit pick on validation.

value={formState.averageProgramsPerMonth}
handleInputChange={handleInputChange}
image="number.png"
min="0"
Copy link
Member

Choose a reason for hiding this comment

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

Nice call on adding validation to these form inputs. Would probably put 1 here as if you have no programs a month the calculator isn't going to spit out a very useful answer :)

name="name"
id="name"
value={formState.name}
handleInputChange={handleInputChange}
Copy link
Member

Choose a reason for hiding this comment

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

Can you explain why your handling each individual input change? What are the pros / cons? What would be another approach?

}
};

const calcCaptionMinutes = () => {
Copy link
Member

Choose a reason for hiding this comment

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

Can you explain the pros / cons of doing the validation client side like this?

@@ -0,0 +1,90 @@
body {
Copy link
Member

Choose a reason for hiding this comment

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

Looks like your using a tailwind and some general styles? Can you explain why?

@@ -1,5 +1,16 @@
const baseConfig =
Copy link
Member

Choose a reason for hiding this comment

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

cool seeing it deployed. Thanks!

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.

2 participants