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
To support SAPs binding DSL we need to be able to parse all three types of bindings
{model>/some/path here/123}
{just/the/path}
{ path: 'my/path', formatter: '.formatterFunction' }
{= ${my/Path}.isCool() === true }
But to do this, someone who understands GrammarKit is required.
This would enable features like go to formatter, go to type, model name completion etc.
go to formatter
go to type
The text was updated successfully, but these errors were encountered:
Additional test cases would be:
{i18n>My.Crazy.Key}
{i18n>This is a longer sentence}
Sorry, something went wrong.
No branches or pull requests
To support SAPs binding DSL we need to be able to parse all three types of bindings
{model>/some/path here/123}
or{just/the/path}
{ path: 'my/path', formatter: '.formatterFunction' }
{= ${my/Path}.isCool() === true }
But to do this, someone who understands GrammarKit is required.
This would enable features like
go to formatter
,go to type
, model name completion etc.The text was updated successfully, but these errors were encountered: