GPAL.RESTClient is the general-purpose fluent REST client behind GPAL.OttoMagicClient. Point it at any API base, pick an ApiEndpoint, and chain calls together with AndThen<T>() - each step's result can be named and reused by a later step, building a multi-step browser workflow out of individual REST calls.
This is a trimmed version of the actual test program. It builds a RESTClient pointed at the OttoMagic REST API, reads a product name off the page, types it into a search box, reads the resulting URL, and navigates to it - each step feeding the next through named results.
using System;
using GenerallyPositive;
using static GenerallyPositive.Enums;
GPAL.WithUseOttoMagic(@"C:OttoMagic").WithPublishToConsole();
RESTClient client = GPAL.RESTClient
.WithAPIBase(GPAL.OttoMagicRestApiBaseUrl)
.WithName("ChainClient")
.WithEndpoint(ApiEndpoint.Evaluate)
.WithXPath("//div[@class='product-name']")
.WithResultName("productName")
.AndThen<string>() // Result 0: "Laptop"
.WithEndpoint(ApiEndpoint.FillInOverwrite)
.WithXPath("//input[@id='search']")
.WithTextFromResult("productName") // Use Result "productName": "Laptop"
.WithResultName("inputResult")
.AndThen() // Submits "Laptop" to the input field
.WithEndpoint(ApiEndpoint.GetCurrentUrl)
.WithResultName("currentUrl")
.AndThen<string>() // Result 1: "http://localhost:3000/search?q=Laptop"
.WithEndpoint(ApiEndpoint.Goto)
.WithUrlFromResult("currentUrl") // Use Result "currentUrl"
.AndThen(); // Navigates to the URL
var results = client.GetExecutionResults();
Console.WriteLine($"Product Name (Result 0): {results[0]}");
Console.WriteLine($"Current URL (Result 1): {results[1]}");
WithAPIBase points the client at any REST API base URL - here, GPAL.OttoMagicRestApiBaseUrl, the local OttoMagic server. WithName labels the client for logging. From here you configure each call with WithEndpoint and whatever With* parameters that endpoint needs.
RESTClient client = GPAL.RESTClient
.WithAPIBase(GPAL.OttoMagicRestApiBaseUrl)
.WithName("ChainClient")
GPAL.OttoMagicClient skips the WithAPIBase call by pointing at GPAL.OttoMagicRestApiBaseUrl automatically, but it's the same RESTClient underneath. Anything you can do with one, you can do with the other.
WithEndpoint picks the operation - Evaluate runs an XPath lookup. WithXPath supplies the path, WithResultName labels the outcome "productName", and AndThen<string>() executes the call, returning a string and storing it both by name and by ordinal position (Result 0).
client
.WithEndpoint(ApiEndpoint.Evaluate)
.WithXPath("//div[@class='product-name']")
.WithResultName("productName")
.AndThen<string>(); // Result 0: "Laptop"
WithTextFromResult("productName") pulls the value stored under that name from the previous step and uses it as the text for FillInOverwrite. AndThen() without a type parameter runs the call without expecting a typed return - useful for actions like filling in a field where you don't need the result value itself.
client
.WithEndpoint(ApiEndpoint.FillInOverwrite)
.WithXPath("//input[@id='search']")
.WithTextFromResult("productName") // Use Result "productName": "Laptop"
.WithResultName("inputResult")
.AndThen(); // Submits "Laptop" to the input field
Results can be looked up by the name given to WithResultName, or by their ordinal position in GetExecutionResults() (Result 0, Result 1, ...). Mixing both in the same chain is fine - use whichever is clearer for a given step.
GetCurrentUrl reads the page's current URL into "currentUrl". The final step uses WithUrlFromResult to plug that value into a Goto call - the chain ends by navigating using a value the workflow itself produced two steps earlier.
client
.WithEndpoint(ApiEndpoint.GetCurrentUrl)
.WithResultName("currentUrl")
.AndThen<string>() // Result 1
.WithEndpoint(ApiEndpoint.Goto)
.WithUrlFromResult("currentUrl")
.AndThen();
var results = client.GetExecutionResults();
Console.WriteLine($"Current URL (Result 1): {results[1]}");
Showing off some plain text in these paragraphs eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Here you can find different accents and emphasis sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
This is a link and how it could look like bestlinkinthebeautifulworld. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Here's just some classic bold text adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam notBoldSecondbestlinkinthebeautifulworld illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Obcaecati, iste distinctio veritatis eligendi laboriosam adipisicing elit illo nostrum corporis at adipisicing elit libero vel voluptas? Expedita, adipisicing facere dolores voluptatem ad ab rem assumenda soluta!
Other cuple of colors in case we want to emphasize several ways adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam adipisicing elit illo nostrum corporis at voluptatem libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta! Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quod veniam, quam ad expedita laborum sed at voluptates culpa ipsam ut vel. Ullam temporibus a mollitia quod aliquam ratione exercitationem nesciunt.
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta! Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quod veniam, quam ad expedita laborum sed at voluptates culpa ipsam ut vel. Ullam temporibus a mollitia quod aliquam ratione exercitationem nesciunt.
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Repudiandae quas consequuntur illo numquam assumenda autem exercitationem distinctio perspiciatis in natus. Eius dicta similique ipsam ipsa minima, nemo quae enim tempore.
GPAL
.CallIfNotFound(GenericCallIfNotFound)
.WithPublishToConsole();
//System.Drawing.Rectangle windowSize = new System.Drawing.Rectangle(10, 10, 1500, 1024);
// NOTE: we have to set browser = before we execute any steps
// this is due to the 'GenericCallIfNotFound' which might throw an exception, and BankScraper will not have the browser set when it calls scraper.Close()
// until the complete fluent line gets executed (meaning every step, meaning browser is not set until everything else succeeds)
browser = GPAL.Browser
.WithBrowserType(Enums.BrowserType.Chrome)
.WithProfileDataDirectory(ChromeProfileLocation)
.WithUseAutomationEngine(AutomationEngine.Selenium)
.WithWindowSize(new System.Drawing.Rectangle(0,0,1920,1080))
.ToGPALObject();