api: wire engine and render endpoints to core #21
Loading…
Reference in a new issue
No description provided.
Delete branch "api/engine"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #15.
What changed
rgxr-core;/rendercallsrgxr-render::render_svg(both merged). The interim 501 helper and its tests are gone.spawn_blocking): subset construction and products are CPU-bound and exponential in the worst case, and must not stall async workers.FaError::Regex→ 400invalid_regex; every otherFaError→ 400invalid_fa;RenderError::Dot→ 400invalid_fa;Unavailable→ 503render_unavailable;Failed→ 500internal, with the detail logged, not returned.invalid_request) and the latex gate are unchanged.RenderResponse.engineserializesrgxr_render::Engine: same lowercase wire values as before.to_dfaand the product constructions stop at 10,000 states and return 400invalid_fa("would build more than 10000 states"). Same denial-of-service class as thefa_to_regexfix in !14, now that these run on request paths.Gates
The ignored test is render's
to_dot_renders_epsilon_glyph; it passes with-- --ignored. Un-ignoring it is opencode's (see #20).New api tests cover real results for run (trace with
symbol: null), union naming,L \ Lempty, concatenation#knaming, the to_dfa → minimize → complement pipeline, regex round trip,invalid_regexmapping, the empty-language →invalid_fapath, the latex gate, andinvalid_fabefore rendering. The router-level/api/v1/runtest now asserts 200 + trace.Semantic decisions