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

feat(DialogFooter): refactored dialog footer to functional component #6817

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

ahmadJT
Copy link
Contributor

@ahmadJT ahmadJT commented May 22, 2024

Fixes #6289

Checklist

  • Includes tests
  • Update documentation

Changes proposed in this pull request:

  • refactored dialog footer to functional component

Reviewers should focus on:

  • DialogFooter

Screenshot

@changelog-app
Copy link

changelog-app bot commented May 22, 2024

Generate changelog in packages/core/changelog/@unreleased

What do the change types mean?
  • feature: A new feature of the service.
  • improvement: An incremental improvement in the functionality or operation of the service.
  • fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
  • break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
    and external consumers of the service's API (e.g. customer-written software or integrations).
  • deprecation: Advertises the intention to remove service functionality without any change to the
    operation of the service itself.
  • manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
    performing database surgery, ...) at the time of upgrade for it to succeed.
  • migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?
  • ❗The break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
  • ✨ All others will result in a minor version release.

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

feat(DialogFooter): refactored dialog footer to functional component

Check the box to generate changelog(s)

  • Generate changelog entry

Copy link
Contributor

@ggdouglas ggdouglas left a comment

Choose a reason for hiding this comment

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

Requesting some minor changes, but otherwise looking good

{actions && <div className={Classes.DIALOG_FOOTER_ACTIONS}>{actions}</div>}
</div>
);
};
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add displayName here?

Suggested change
};
};
DialogFooter.displayName = `${DISPLAYNAME_PREFIX}.DialogFooter`;

return <div className={Classes.DIALOG_FOOTER_MAIN_SECTION}>{this.props.children}</div>;
}

/** Optionally render the footer actions (right aligned). */
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we preserve these comments in the refactored structure of the component?

{/* Render the main footer section (left aligned). */}
<div className={Classes.DIALOG_FOOTER_MAIN_SECTION}>{children}</div>
{/* Optionally render the footer actions (right aligned). */}
{actions && <div className={Classes.DIALOG_FOOTER_ACTIONS}>{actions}</div>}

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.

Refactor simple class components into functions
3 participants