You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some components seem to be meant as examples, other are just wrapping things with no additional benefit. Listing what's done and what's lacking will allow cleaning things up.
Base components
bc-datalog-editor
Reads datalog code from an attribute or a child node. Handles syntax highlight, but does not run any computation; parse errors and policy/checks *
highlights have to be provided through attributes
It can be made read-only, to display syntax-highlighted datalog (eg from a token, or generated facts)
bc-authorizer-editor
Just wraps bc-datalog-editor with no added feature. This one could go, imo.
bc-authorizer-content
This one takes a series of facts, groups them by name and displays them in a read-only datalog-editor
bc-authorizer-result
This one takes the authorization result returned by the library and displays it in a human readable way
bc-token-content
This one only displays what's passed to an attribute in a pre block. It could go imo
High-level components
bc-token-printer
This one takes a b64-encoded token, displays the parsed blocks, and optionally lets run an authorizer on it. The encoded token can be provided as an attribute or pasted in a textarea
bc-datalog-example
It provides a playground for datalog computation. It's not working properly and is subsumed by bc-datalog-playground
bc-authorizer-example
Same as datalog example, but also displays checks and policies results. It could be subsumed by datalog-playground with little effort
bc-full-example
Same as authorizer example, but also takes token blocks. It could either be subsumed by datalog-playground or token-printer, or stay separate.
bc-token-editor
This one provides a way to edit multiple blocks m, but does not generate tokens or run authorizers. It could be evolved into a token generator.
The text was updated successfully, but these errors were encountered:
Some components seem to be meant as examples, other are just wrapping things with no additional benefit. Listing what's done and what's lacking will allow cleaning things up.
Base components
bc-datalog-editor
Reads datalog code from an attribute or a child node. Handles syntax highlight, but does not run any computation; parse errors and policy/checks *
highlights have to be provided through attributes
It can be made read-only, to display syntax-highlighted datalog (eg from a token, or generated facts)
bc-authorizer-editor
Just wraps
bc-datalog-editor
with no added feature. This one could go, imo.bc-authorizer-content
This one takes a series of facts, groups them by name and displays them in a read-only datalog-editor
bc-authorizer-result
This one takes the authorization result returned by the library and displays it in a human readable way
bc-token-content
This one only displays what's passed to an attribute in a
pre
block. It could go imoHigh-level components
bc-token-printer
This one takes a b64-encoded token, displays the parsed blocks, and optionally lets run an authorizer on it. The encoded token can be provided as an attribute or pasted in a textarea
bc-datalog-example
It provides a playground for datalog computation. It's not working properly and is subsumed by
bc-datalog-playground
bc-authorizer-example
Same as datalog example, but also displays checks and policies results. It could be subsumed by datalog-playground with little effort
bc-full-example
Same as authorizer example, but also takes token blocks. It could either be subsumed by datalog-playground or token-printer, or stay separate.
bc-token-editor
This one provides a way to edit multiple blocks m, but does not generate tokens or run authorizers. It could be evolved into a token generator.
The text was updated successfully, but these errors were encountered: