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 Less Syntax #34

Merged
merged 4 commits into from
Jul 16, 2023
Merged

Fix Less Syntax #34

merged 4 commits into from
Jul 16, 2023

Conversation

confused-Techie
Copy link
Member

This PR a conjoined effort of myself and @DeeDeeG resolves the issues in our style sheets for this package, that are now causing breakage after the Pulsar v1.107.0 release.

When/If merged, an update of this repo within Pulsar should constitute a hotfix release, to ensure end users are not effected

Copy link
Member

@DeeDeeG DeeDeeG left a comment

Choose a reason for hiding this comment

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

Changes appear to be exactly as intended: Adding parentheses around uncontained / non-parentheses-bound instances of math (especially/most pressingly the division / operation).

This is for compatibility with Less 4.x, which required this change. It should be totally back-compatible with older Less, since these parentheses were always allowed before, they are only just now being required to reduce ambiguity with other recent web platform features, if I recall correctly.

In looking over all the files as fast as I could while being thorough, I did not notice any syntax errors.

Furthermore, when using Pulsar to do a "Find in Project" search in this repo locally, under the styles/ subdir, with this regex (?<!\/)\/[^\/\n] provided by @asiloisad on the Discord (thanks!!), I can see that all instances of division / are in parentheses now.

Great! 👍

@confused-Techie confused-Techie merged commit aae1c73 into master Jul 16, 2023
@confused-Techie confused-Techie deleted the fix-less-syntax branch July 16, 2023 04:48
@DeeDeeG
Copy link
Member

DeeDeeG commented Jul 16, 2023

As always... CI failing is unrelated to these changes. CI was not set up in a working fashion since the fork from upstream. So, I will be ignoring the results of CI.

I note that there are no "green"/passing runs in this forked repo as of yet.

@confused-Techie
Copy link
Member Author

Yeah, might be good to give some love here soon, to find out why the CI is so unhappy, may or may not be related to the several GraphQL updates from the github actions waiting around in this repo

@DeeDeeG
Copy link
Member

DeeDeeG commented Jul 16, 2023

Before (broken in Pulsar v1.107.0):

github package with not very good spacing between elements

After (With fix):

github package with better spacing between elements

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