Parse simple expressions #389

raxbg · 2022-09-19T09:42:11Z

Fixes #388
Builds on top of #390

sabberworm · 2022-09-20T19:00:19Z

tests/ParserTest.php

+    public function functionArithmeticInFile()
+    {
+        $oDoc = self::parsedStructureForFile('function-arithmetic', Settings::create()->withMultibyteSupport(true));
+        $sExpected = 'div {height: max(300,vh + 10);}


AFAICT, vh without a number in front is still not valid and I’d prefer it would throw an error in strict mode.

Indeed, it is invalid, however this seems to be outside of the scope of these changes. I guess we need a separate issue for this. Also is it a concern of the parser to validate the semantic meaning of identifiers it encounters?

Also is it a concern of the parser to validate the semantic meaning of identifiers it encounters?

I agree it's not.

Moving forwards, we've agreed to replace strict mode parsing with a logging mechanism. And try to replicate what most browsers do when encountering invalid syntax. A unit with no number in front should therefore probably be parsed as zero of that unit. And, as a bonus, a separate PR would log the lack of a number.

So, for now, we don't need to worry about strict mode, but should create issues for things that could be logged in future.

westonruter · 2023-03-15T23:50:07Z

For what it's worth, I'm including this patch in ampproject/amp-wp#7487 and it is passing all tests in our project.

westonruter · 2024-02-07T18:01:21Z

@oliverklee was this closed as well as other PRs (e.g. #185 and #193) just because the master branch was deleted?

oliverklee · 2024-02-07T18:03:19Z

@westonruter Oh no! It indeed was. ;-(

oliverklee · 2024-02-07T18:03:54Z

I have now reinstated the legacy master branch and will reopen the PRs in a minute. So sorry for this.

sabberworm · 2024-02-07T20:09:55Z

I have now reinstated the legacy master branch and will reopen the PRs in a minute. So sorry for this.

I would prefer we delete the master branch and just change all the PRs to point to main instead.

oliverklee · 2024-02-07T21:02:26Z

@sabberworm Oh, I wasn't aware that this was possible in the first place! Will do.

oliverklee · 2024-02-07T22:40:13Z

I have now moved all PRs over to main and dropped the master branch again.

JakeQZ

I like this. I'd be happy for this to be merged. @oliverklee, @sabberworm WDYT?

JakeQZ · 2024-02-15T02:24:50Z

tests/ParserTest.php

+    public function functionArithmeticInFile()
+    {
+        $oDoc = self::parsedStructureForFile('function-arithmetic', Settings::create()->withMultibyteSupport(true));
+        $sExpected = 'div {height: max(300,vh + 10);}


Also is it a concern of the parser to validate the semantic meaning of identifiers it encounters?

I agree it's not.

Moving forwards, we've agreed to replace strict mode parsing with a logging mechanism. And try to replicate what most browsers do when encountering invalid syntax. A unit with no number in front should therefore probably be parsed as zero of that unit. And, as a bonus, a separate PR would log the lack of a number.

So, for now, we don't need to worry about strict mode, but should create issues for things that could be logged in future.

JakeQZ · 2024-02-15T02:28:47Z

src/Value/CSSFunction.php

+    /**
+     * @param ParserState $oParserState
+     * @param bool $bIgnoreCase
+     *
+     * @return string
+     *
+     * @throws SourceException
+     * @throws UnexpectedEOFException
+     * @throws UnexpectedTokenException
+     */
+    public static function parseName(ParserState $oParserState, $bIgnoreCase = false)
+    {
+        return $oParserState->parseIdentifier($bIgnoreCase);
+    }
+
+    /**
+     * @param ParserState $oParserState
+     *
+     * @return array
+     *
+     * @throws SourceException
+     * @throws UnexpectedEOFException
+     * @throws UnexpectedTokenException
+     */
+    public static function parseArgs(ParserState $oParserState)
+    {
+        return Value::parseValue($oParserState, ['=', ' ', ',']);
+    }
+


Nice refactoring. Could this be put through as a separate PR?

JakeQZ

We need a changelog entry, though.

JakeQZ · 2024-02-15T02:39:37Z

src/Value/Expression.php

+<?php
+
+namespace Sabberworm\CSS\Value;
+
+use Sabberworm\CSS\OutputFormat;
+use Sabberworm\CSS\Parsing\ParserState;
+
+/**
+ * An `Expression` represents a special kind of value that is comprised of multiple components wrapped in parenthesis.
+ * Examle `height: (vh - 10);`.
+ */
+class Expression extends CSSFunction
+{
+    /**
+     * @param ParserState $oParserState
+     * @param bool $bIgnoreCase
+     *
+     * @return Expression
+     *
+     * @throws SourceException
+     * @throws UnexpectedEOFException
+     * @throws UnexpectedTokenException
+     */
+    public static function parse(ParserState $oParserState, $bIgnoreCase = false)
+    {
+        $oParserState->consume('(');
+        $aArguments = self::parseArgs($oParserState);
+        $mResult = new Expression("", $aArguments, ',', $oParserState->currentLine());
+        $oParserState->consume(')');
+        return $mResult;
+    }
+}


There should be a class-specific unit test for this new class. The overall parser tests are good, but we also want to make sure each individual class behaves as it should.

@raxbg, would you be willing to create a corresponding TestExpression class to test this new class as a standalone?

There should be a class-specific unit test for this new class. The overall parser tests are good, but we also want to make sure each individual class behaves as it should.

Makes sense. How does that look like: 14118a2

JakeQZ · 2024-02-15T03:08:04Z

I like this. I'd be happy for this to be merged. @oliverklee, @sabberworm WDYT?

On further looking, a class-specific unit test is also needed for the new class (inherited from the terribly misnomered TestCase - Rename That!).

oliverklee · 2024-02-15T09:34:41Z

Also, according to the original commit message, this builds on on top of #390. So we should get that in first and then rebase.

oliverklee

Let's get #390 in first.

raxbg · 2024-07-10T12:13:38Z

#390 is closed now and seems like it's no longer needed. There shouldn't be anything else blocking the merge of this PR :)

Let me know if you have any concerns

raxbg added 8 commits September 19, 2022 12:33

Parse simple expressions

908bc46

Support arithmetic ops (+,-,*,/) in functions

093c527

Add tests for arithmetic in functions

f734920

Merge branch 'fix/arithmetic-in-functions' into fix/expression-parsing

7da6868

Use CSSFunction::parseArgs when parsing expression arguments

8627ef6

Handle arithmetic operators in Value

184b610

Merge branch 'fix/arithmetic-in-functions' into fix/expression-parsing

9386fe9

Fix tests

d9f89cc

sabberworm reviewed Sep 20, 2022

View reviewed changes

Merge branch 'upstream_master' into fix/expression-parsing

db4d18b

westonruter mentioned this pull request Mar 15, 2023

Fix failure to parse complex CSS values ampproject/amp-wp#7487

Merged

oliverklee deleted the branch MyIntervals:main February 7, 2024 11:36

oliverklee closed this Feb 7, 2024

oliverklee reopened this Feb 7, 2024

oliverklee changed the base branch from master to main February 7, 2024 22:34

JakeQZ reviewed Feb 15, 2024

View reviewed changes

JakeQZ requested a review from oliverklee February 15, 2024 02:30

JakeQZ requested changes Feb 15, 2024

View reviewed changes

oliverklee requested changes Feb 15, 2024

View reviewed changes

westonruter mentioned this pull request Feb 15, 2024

Bump PHP-CSS-Parser to v8.5.1 ampproject/amp-wp#7742

Merged

2 tasks

This was referenced Jun 22, 2024

[FEATURE] Support arithmetic operators in CSS functions #607

Merged

Test expressions involing brackets #621

Open

raxbg added 4 commits July 10, 2024 13:18

Make the check for arithmetic operators strict

ca89a71

Merge branch 'main' into fix/expression-parsing

7aaebb2

Catch up with upstream/main

abbcc8f

Add class-specific tests for CSS\Value\Expression

14118a2

westonruter mentioned this pull request Nov 5, 2024

Bump sabberworm/php-css-parser from 8.5.1 to 8.7.0 ampproject/amp-wp#7904

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Parse simple expressions #389

Parse simple expressions #389

raxbg commented Sep 19, 2022 •

edited

Loading

sabberworm Sep 20, 2022

raxbg Sep 21, 2022

JakeQZ Feb 15, 2024 •

edited

Loading

westonruter commented Mar 15, 2023

westonruter commented Feb 7, 2024

oliverklee commented Feb 7, 2024

oliverklee commented Feb 7, 2024

sabberworm commented Feb 7, 2024

oliverklee commented Feb 7, 2024

oliverklee commented Feb 7, 2024

JakeQZ left a comment

JakeQZ Feb 15, 2024 •

edited

Loading

JakeQZ Feb 15, 2024

JakeQZ left a comment

JakeQZ Feb 15, 2024 •

edited

Loading

JakeQZ Feb 15, 2024 •

edited

Loading

raxbg Jul 10, 2024

JakeQZ commented Feb 15, 2024

oliverklee commented Feb 15, 2024

oliverklee left a comment

raxbg commented Jul 10, 2024

Parse simple expressions #389

Are you sure you want to change the base?

Parse simple expressions #389

Conversation

raxbg commented Sep 19, 2022 • edited Loading

sabberworm Sep 20, 2022

Choose a reason for hiding this comment

raxbg Sep 21, 2022

Choose a reason for hiding this comment

JakeQZ Feb 15, 2024 • edited Loading

Choose a reason for hiding this comment

westonruter commented Mar 15, 2023

westonruter commented Feb 7, 2024

oliverklee commented Feb 7, 2024

oliverklee commented Feb 7, 2024

sabberworm commented Feb 7, 2024

oliverklee commented Feb 7, 2024

oliverklee commented Feb 7, 2024

JakeQZ left a comment

Choose a reason for hiding this comment

JakeQZ Feb 15, 2024 • edited Loading

Choose a reason for hiding this comment

JakeQZ Feb 15, 2024

Choose a reason for hiding this comment

JakeQZ left a comment

Choose a reason for hiding this comment

JakeQZ Feb 15, 2024 • edited Loading

Choose a reason for hiding this comment

JakeQZ Feb 15, 2024 • edited Loading

Choose a reason for hiding this comment

raxbg Jul 10, 2024

Choose a reason for hiding this comment

JakeQZ commented Feb 15, 2024

oliverklee commented Feb 15, 2024

oliverklee left a comment

Choose a reason for hiding this comment

raxbg commented Jul 10, 2024

raxbg commented Sep 19, 2022 •

edited

Loading

JakeQZ Feb 15, 2024 •

edited

Loading

JakeQZ Feb 15, 2024 •

edited

Loading

JakeQZ Feb 15, 2024 •

edited

Loading

JakeQZ Feb 15, 2024 •

edited

Loading