When loading Parasol without Seaside, #withCapabilities: fails

[koendehondt]

The readme states:

Warning: Parasol's default baseline will NOT load Seaside automatically. You can therefore use Parasol without Seaside, but then you should only load the 'core' Metacello group. The 'default' Metacello group pulls in the extensions for Seaside but you are required to load Seaside yourself. This ensures you can load your own version of Seaside without tackling Metacello load conflicts. Only the 'tests' Metacello group will load latest master of Seaside.

I like to test a web application which is not a Seaside application. So, I do not need Seaside. That was my expectation.

But when I load Parasol with:

Metacello new
    baseline: 'Parasol';
    repository: 'github://SeasideSt/Parasol:master/repository';
    load: 'default'.

BPRemoteWebDriver withCapabilities: BPChromeOptions new fails with: Message not understood: Dictionary >> #asJson, because asJson is not part of Parasol. It is part of Seaside.

Since I do not need Seaside, I do not want to load it.

So, either I made a mistake, or either the documentation in the readme is not correct. Please advise. Thank you.

[jbrichau]

Hey Koen,

Thanks for reporting.

I had indeed introduced this dependency again in 368d592

I believe we had experienced some issues by relying on another JSON parser before, which is why I added the WAJsonParser as the default anyway.

This should therefore now be fixed again in Pharo.

[koendehondt]

@jbrichau Thank you for the quick answer. However, I used Pharo 13, so I am confused when you write "This should therefore now be fixed again in Pharo.".

[jbrichau]

@koendehondt Because the merge of the PR that closed this issue should have fixed it: #71
So, you should pull in the latest master version.

In Pharo 9 and later, the STONJSON class is now used to read JSON.

[koendehondt]

@jbrichau

#71 does not fix the issue. Please load Parasol with:

Metacello new
    baseline: 'Parasol';
    repository: 'github://SeasideSt/Parasol:master/repository';
    load: 'default'.

and then evaluate:

BPRemoteWebDriver withCapabilities: BPChromeOptions new.

Then you will see that the issue is in BPSmalltalkPlatform>>#jsonWrite::

[jbrichau]

@koendehondt Sorry about that.
I now also removed that dependency in PR #72 but since we have no tests that actually run without Seaside being loaded, I have to manually test. I will keep this issue open to add a test that verifies basic functionality without Seaside being loaded.

I will merge the PR later when the tests are green.

Let me know if you hit other issues when running standalone.

[koendehondt]

@jbrichau

No problem :-)

The change in #72 is fine. I tried it. I can run Parasol tests without loading Seaside. I only tried in Pharo 13.