We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checklist
--dev
Playground link
Catalyst attributes are dasherised when serialised to HTML, which the Catalyst plugin does not quite properly reflect.
Expected behavior
The following code:
import { controller, attr } from '@github/catalyst' @controller class HelloWorldElement extends HTMLElement { @attr fooBar = 'hello' }
Would result in an attribute of data-foo-bar in Catalyst 1.x and an attribute of foo-bar in 2.x and so the attributes json should be:
data-foo-bar
foo-bar
attributes
"attributes": [ { "name": "data-foo-bar", // just `foo-bar` in v2 "type": { "text": "string" }, "default": "'hello'", "fieldName": "fooBar" } ],
Actual behavior
The generated manifest has the following:
"attributes": [ { "name": "fooBar", "type": { "text": "string" }, "default": "'hello'", "fieldName": "fooBar" } ],
The text was updated successfully, but these errors were encountered:
@keithamus Could you take a look at this PR to make sure I got it right? 🙂 Thanks #188
Sorry, something went wrong.
No branches or pull requests
Checklist
--dev
flag to get more information?Playground link
Catalyst attributes are dasherised when serialised to HTML, which the Catalyst plugin does not quite properly reflect.
Expected behavior
The following code:
Would result in an attribute of
data-foo-bar
in Catalyst 1.x and an attribute offoo-bar
in 2.x and so theattributes
json should be:Actual behavior
The generated manifest has the following:
The text was updated successfully, but these errors were encountered: