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

fix: progressbar component #27

Merged
merged 5 commits into from
Oct 10, 2020
Merged

fix: progressbar component #27

merged 5 commits into from
Oct 10, 2020

Conversation

fayez-baig
Copy link
Owner

No description provided.


export interface ProgressBarProps {
color?: Color;
max: number;
Copy link
Collaborator

Choose a reason for hiding this comment

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

What if I dont want to pass max ? can we make it optional ?

Copy link
Owner Author

Choose a reason for hiding this comment

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

if we dont provide how can we determine length

Copy link
Collaborator

Choose a reason for hiding this comment

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

Did you not provide a default for it already ?

Copy link
Owner Author

Choose a reason for hiding this comment

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

provided

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes, that what I mean.... we can make it optional !

Copy link
Owner Author

Choose a reason for hiding this comment

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

done

export interface ProgressBarProps {
color?: Color;
max: number;
progressBarSize?: Size;
Copy link
Collaborator

Choose a reason for hiding this comment

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

lets make it simple, size !!

<ProgressBar {...args} />
);

export const Indeterminate = indeterminateProgressBarTemplate.bind({});
Copy link
Collaborator

Choose a reason for hiding this comment

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

How does this Indeterminate work ? what is the diff ?

Copy link
Owner Author

Choose a reason for hiding this comment

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

it keeps on loading

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes, but from a component API point of view, what props do we need for this

Copy link
Owner Author

Choose a reason for hiding this comment

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

if we don't provide a value prop it keeps on loading till it receives a value prop

Copy link
Collaborator

Choose a reason for hiding this comment

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

cool !

@@ -34,12 +35,11 @@ export default {

const defaultNotificationTemplate: Story<NotificationProps> = args => (
<Notification {...args}>
{/* replace p with text component after all merge */}
<p>
<Text>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice one ! Can you also check if we can add various classes to this text component ?
Check the usage of p tag in Column and Grid components !

Copy link
Owner Author

Choose a reason for hiding this comment

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

replaced

Copy link
Collaborator

Choose a reason for hiding this comment

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

where and when ? and how about those classes for p tag ?

Copy link
Owner Author

Choose a reason for hiding this comment

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

I haven't done any changes in the extension component

Copy link
Owner Author

Choose a reason for hiding this comment

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

will do that later in different PR

Copy link
Collaborator

Choose a reason for hiding this comment

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

I am talking about this in Grid story

<Col key={i} {...args}>
	<p
		className={colContentClasses}
		style={{ padding: '16px 0px', textAlign: 'center' }}>
		<code>{col + ++i}</code>
	</p>
</Col>

Copy link
Owner Author

Choose a reason for hiding this comment

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

oh but our text does accept any className props let me add that

Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice one ! Can you also check if we can add various classes to this text component ?
Check the usage of p tag in Column and Grid components !

That's what I meant in this comment !! @fayez-baig

Copy link
Collaborator

Choose a reason for hiding this comment

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

keep it for future, let's develop components now ! this refactoring we have to do anyway in the future ! you see.... the discussion has diverted from progress bar component !. That;s why I hate adding multiple stuff in a single PR !

@@ -21,10 +22,11 @@ const defaultBoxTemplate: Story<BoxProps> = args => (
<article className={getStyles(['media'])}>
<div className={getStyles(['media-left'])}>
<figure className={getStyles(['image is-64x64'])}>
<img
<Image
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice one 👍

@faran4engg
Copy link
Collaborator

First of all, lets not mix diff stuf in single PR, if we need to replace all the component with Text for example. then a PR should be created only for replacement of Text. Nothing much. if you mix many stuff. it will be difficult to catch bugs here ! @fayez-baig

@fayez-baig
Copy link
Owner Author

okay

@fayez-baig
Copy link
Owner Author

okay, from next time onwards I will raise a separate PR for changes

@faran4engg
Copy link
Collaborator

okay, from next time onwards I will raise a separate PR for changes

@faran4engg
Copy link
Collaborator

First of all, lets not mix diff stuf in single PR, if we need to replace all the component with Text for example. then a PR should be created only for replacement of Text. Nothing much. if you mix many stuff. it will be difficult to catch bugs here ! @fayez-baig

you may need to test every component now as you have changed so many little stuff in majority of the components ! @fayez-baig @rifaq-ahmer

Copy link
Collaborator

@faran4engg faran4engg left a comment

Choose a reason for hiding this comment

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

I approve this. but next time please dont make a Bhel Puri stuff in the PR. @fayez-baig

@fayez-baig
Copy link
Owner Author

yes I have told @rifaq-ahmer to check all the props

@fayez-baig
Copy link
Owner Author

okay I will try to keep it clean

@fayez-baig fayez-baig merged commit 0e62099 into develop Oct 10, 2020
@faran4engg
Copy link
Collaborator

yes I have told @rifaq-ahmer to check all the props

check thoroughly and deploy storybook

@faran4engg
Copy link
Collaborator

I dont see chlidren prop working in Box component ! is it a bug ? or you have not tested properly ?

@faran4engg
Copy link
Collaborator

lets discuss separetly.. not in this merged PR !

@fayez-baig
Copy link
Owner Author

🎉 This PR is included in version 1.0.11 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants