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: migrate Bootstrap from 3.3.7 to 5.3.3 #1654

Merged
merged 2 commits into from
Oct 15, 2024

Conversation

leovan
Copy link
Contributor

@leovan leovan commented Oct 4, 2024

  1. Migrate Bootstrap from 3.3.7 to 5.3.3
  2. Remove jQuery dependency
  3. Fix config updating when using config_file
  4. Some UI update:
    • Replace abbr with tooltip
    • Replace code with badge when showing alert

@fabclmnt
Copy link
Contributor

Hi @leovan ,

can you please attach an html report that would result of using this branch to generate a profile report?

That would ease the PR review from a functional perspective.

@fabclmnt fabclmnt self-requested a review October 15, 2024 13:15

@property
def alert_type_name(self) -> str:
return self.alert_type.name.replace("_", " ").lower().title()
return self.alert_type.name.replace("_", " ").capitalize()
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice catch!

@fabclmnt fabclmnt changed the title Migrate Bootstrap from 3.3.7 to 5.3.3 feat: migrate Bootstrap from 3.3.7 to 5.3.3 Oct 15, 2024
@fabclmnt
Copy link
Contributor

Also change the PR title to follow the expected naming and convention of the package. Otherwise this would break the release and computation of the release version.

Added feat:.

@fabclmnt fabclmnt changed the base branch from develop to feat/bootstrap_updt October 15, 2024 14:37
@fabclmnt fabclmnt merged commit e990f90 into ydataai:feat/bootstrap_updt Oct 15, 2024
12 of 14 checks passed
@leovan
Copy link
Contributor Author

leovan commented Oct 15, 2024

Hi @leovan ,

can you please attach an html report that would result of using this branch to generate a profile report?

That would ease the PR review from a functional perspective.

All examples were tested with to_file, here are some reports.

examples/titanic/titanic.py:

titanic_report.zip

examples/usaairquality/usaairquality.py:

Ts_Profile_1011.zip

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