Skip to content
This repository has been archived by the owner on Oct 6, 2021. It is now read-only.

feat: tracer registration page #18

Closed
wants to merge 5 commits into from
Closed

Conversation

adityapurwa
Copy link
Contributor

@adityapurwa adityapurwa commented Aug 8, 2021

Closes #12

Description

Pendaftaran

Current Tasks

  1. Content board container
  2. Form title
  3. Form text input @adityapurwa
  4. Form text input with prefix
  5. Form select input
  6. Form radio button input @dreamid27
  7. Form validation label @dreamid27
  8. Form password input @dreamid27
  9. Button @dreamid27
  10. Info message component @dreamid27

@netlify
Copy link

netlify bot commented Aug 8, 2021

✔️ Deploy Preview for silacak ready!

🔨 Explore the source changes: 906c3c5

🔍 Inspect the deploy log: https://app.netlify.com/sites/silacak/deploys/611151b8390ac100070c4c97

😎 Browse the preview: https://deploy-preview-18--silacak.netlify.app

@@ -0,0 +1,24 @@
import Head from "next/head";
Copy link
Member

Choose a reason for hiding this comment

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

registration.tsx -> register.tsx - as per the navbar.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do you think "Registration" is semantically better as the navigation word is "Registrasi"?

Copy link
Member

Choose a reason for hiding this comment

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

@adityapurwa Hmm, you're right. Feel free to pick whichever you like, but please update the navbar items accordingly.

Comment on lines +3 to +5
import { ContentBoard } from "~/components/ui/board/content-board/content-board";
import { FormTitle } from "~/components/ui/form/form-title/form-title";
import { FormSubtitle } from "~/components/ui/form/form-subtitle/form-subtitle";
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
import { ContentBoard } from "~/components/ui/board/content-board/content-board";
import { FormTitle } from "~/components/ui/form/form-title/form-title";
import { FormSubtitle } from "~/components/ui/form/form-subtitle/form-subtitle";
import { ContentBoard } from "~/components/ui/board/content-board";
import { FormTitle } from "~/components/ui/form/form-title";
import { FormSubtitle } from "~/components/ui/form/form-subtitle";

Can we compile these exports into each of its root folder? Having the import directory doubled /content-board/content-board doesn't feel like good UX.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Did you mean instead of having ~/components/ui/board/content-board/content-board.tsx, we have ~/components/ui/board/content-board/index.tsx?

Copy link
Member

Choose a reason for hiding this comment

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

@adityapurwa I'm thinking we create an index.ts file and pass all the exports through there, like this:

export * from "./content-board";

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I personally avoid having two ways of importing something.

By grouping and exports into an index.ts, we'd now have two ways of importing. Directly to the component file, and using the index groupings. This would introduce inconsistencies.

It will also be problematic with the go-to source feature, as now clicking on the reference will take us to the index file instead of directly to the file of interest.

What do you think about it? Let me know if the decision stands to use export groupings. 🙌

Copy link
Member

Choose a reason for hiding this comment

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

@adityapurwa If you think the content-board folder only contains this one file, I think it's okay to move the content-board.tsx file one folder up (~/components/ui/board/content-board.tsx).

The export grouping I think is only necessary when the folder contains a lot of components. Since export grouping is already used extensively at WBW, and we want to keep our styleguide as close to it as possible, we'll eventually have to use export grouping when we want to group exports of design system components (e.g. those at ~/components/ui/*).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes you are correct, I agree we can lift the component file outside of its folder. Even when we adds *.test later, I don't think it'd be too crowded. Let's go with uplifting it then 🚀

Copy link
Member

@resir014 resir014 Aug 8, 2021

Choose a reason for hiding this comment

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

Even when we adds *.test later, I don't think it'd be too crowded.

We store tests in a separate __tests__ folder so it wouldn't be a problem regardless. See Jest config for the regex pattern.

@resir014
Copy link
Member

resir014 commented Aug 8, 2021

@adityapurwa ContentBoard also need to be wrapped inside a wrapping component with a flex-1, since the content wont automatically adjust by the screen height if we don't put in a flex.

image

Think HomePageContent, but with a background of grey-100.

@dreamid27
Copy link
Contributor

How can i contribute ?

@adityapurwa
Copy link
Contributor Author

How can i contribute ?

Can you edit the PR description?

If you can, the best way to do it is to edit the PR description, add your name next to the checklist item, then create a branch based on tracer-registration. Subsequent PR then would be directed to tracer-registration instead of directly to main.

I will start listing my name next to the checklist item as well so we don't step on each other toes. What do you think @dreamid27 ?

@adityapurwa
Copy link
Contributor Author

@adityapurwa ContentBoard also need to be wrapped inside a wrapping component with a flex-1, since the content wont automatically adjust by the screen height if we don't put in a flex.

image

Think HomePageContent, but with a background of grey-100.

The content of this form is quite long, are we aiming for a sticky header and footer layout and have the scrollbar inside the middle part?

@dreamid27
Copy link
Contributor

dreamid27 commented Aug 8, 2021

How can i contribute ?

Can you edit the PR description?

If you can, the best way to do it is to edit the PR description, add your name next to the checklist item, then create a branch based on tracer-registration. Subsequent PR then would be directed to tracer-registration instead of directly to main.

Edit this PR? Unfortunately i can't edit the PR..

I will start listing my name next to the checklist item as well so we don't step on each other toes. What do you think @dreamid27 ?

Sure, it will be helping!

@adityapurwa
Copy link
Contributor Author

How can i contribute ?

Can you edit the PR description?
If you can, the best way to do it is to edit the PR description, add your name next to the checklist item, then create a branch based on tracer-registration. Subsequent PR then would be directed to tracer-registration instead of directly to main.

Edit this PR? Unfortunately i can't edit the PR..

I will start listing my name next to the checklist item as well so we don't step on each other toes. What do you think @dreamid27 ?

Sure, it will be helping!

Please comment on which checklist item that you wanted to do, and I will list your name on it.

Thank you @dreamid27 !

@dreamid27
Copy link
Contributor

Form radio button input
Form validation label
Form password input
Button
Info message component

I will take this to do, may I?

@adityapurwa
Copy link
Contributor Author

Form radio button input
Form validation label
Form password input
Button
Info message component

I will take this to do, may I?

Wonderful! Thank you so much for the help. Really appreciated! 🙌
I updated the PR description on parts that you've mentioned.

@resir014
Copy link
Member

resir014 commented Aug 8, 2021

The content of this form is quite long, are we aiming for a sticky header and footer layout and have the scrollbar inside the middle part?

I don't think that'd be a good idea. Let's stick w/ flex-1 instead.

@zainfathoni
Copy link
Member

FYI @adityapurwa @dreamid27, you can start using our Form UI components copied from our wargabantuwarga.com project.

@adityapurwa
Copy link
Contributor Author

Heads up ~ I will not be available this week as I will be out of the city. @dreamid27 , if you want to take over this PR, feel free to do so!

@adityapurwa adityapurwa marked this pull request as ready for review August 9, 2021 16:10
@resir014
Copy link
Member

@dreamid27, please let us know if you can still work on this. We're running short on time so we need to get this done quickly.

@dreamid27
Copy link
Contributor

@dreamid27, please let us know if you can still work on this. We're running short on time so we need to get this done quickly.

Sure guys!

Maybe the task will done tomorrow

@dreamid27 dreamid27 mentioned this pull request Aug 11, 2021
10 tasks
@dreamid27
Copy link
Contributor

dreamid27 commented Aug 11, 2021

You can check the pr here yah :
#42

cc : @zainfathoni @resir014

@resir014
Copy link
Member

Superseded by #42.

@resir014 resir014 closed this Aug 12, 2021
@zainfathoni zainfathoni deleted the tracer-registration branch August 13, 2021 05:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tracer Registration Form
4 participants