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

Litviniuk/replace flex layout with tailwind #2657

Merged
merged 9 commits into from
Dec 2, 2024

Conversation

darynkka
Copy link
Contributor

@darynkka darynkka commented Dec 1, 2024

all flexLayout usages were replaced with Tailwind CSS

package.json Outdated
@@ -71,6 +71,7 @@
"@types/node": "^18.11.9",
"@typescript-eslint/eslint-plugin": "7.5.0",
"@typescript-eslint/parser": "7.5.0",
"autoprefixer": "^10.4.20",
Copy link
Contributor

Choose a reason for hiding this comment

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

Are autoprefix and postcss required? I don't see that you include them in the plugins, maybe we can remove them?

Copy link
Contributor

Choose a reason for hiding this comment

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

Remove @angular/flex-layout when done

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see the removed package in yarn.lock file. Did you use yarn remove <package>?

@@ -12,6 +12,11 @@
}
.wrapper {
margin-top: 16px;
display: flex;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why didn't you use tailwind classes in this case?

max-width: max-content;
line-height: 17px;
color: black;
place-content: flex-start space-between;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why didn't you use tailwind classes in this case?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

because there are the same properties for both elements and there is no reason to dublicate it

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, but you can just use the ready-made tailwind classes, so it shouldn't be a problem.

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 made that change in previous commit as you said


@media (max-width: 1280px) {
.view-control-panel {
display: flex;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why didn't you use tailwind classes in this case?

Copy link

sonarqubecloud bot commented Dec 2, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
D Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@darynkka darynkka merged commit bee9f97 into develop Dec 2, 2024
2 of 3 checks passed
@darynkka darynkka deleted the litviniuk/replace-flexLayout-with-tailwind branch December 2, 2024 19:12
@DmyMi DmyMi restored the litviniuk/replace-flexLayout-with-tailwind branch December 3, 2024 15:09
@DmyMi
Copy link
Contributor

DmyMi commented Dec 3, 2024

comment for future duplicate - we had to revert this pr :)

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.

3 participants