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
This issue is not a bug report. (please use a different template for reporting a bug)
This issue is not a duplicate of an existing issue. (please use the search to find existing issues)
Description
I want to write Cedar Policy Language in Monaco-editor implemented in my web app. I've managed to define 'cedar' as a custom language for me by providing tokens and suggestions. But when it comes to error handling by setting markers in the editor, it is tough to handle user-written code in editor by checking every nested bracket. There is a vs-code extension for Cedar language. Can we use that extension directly in the Monaco editor?
Please let me know how I manage to handle error handling like vs-code in my custom-defined language for each and every small rule of the nested bracket without defining it from scratch.
Context
Description
I want to write Cedar Policy Language in Monaco-editor implemented in my web app. I've managed to define 'cedar' as a custom language for me by providing tokens and suggestions. But when it comes to error handling by setting markers in the editor, it is tough to handle user-written code in editor by checking every nested bracket. There is a vs-code extension for Cedar language. Can we use that extension directly in the Monaco editor?
Please let me know how I manage to handle error handling like vs-code in my custom-defined language for each and every small rule of the nested bracket without defining it from scratch.
Monaco Editor Playground Link
No response
Monaco Editor Playground Code
permit (
principal == PhotoApp::User::"alice",
action == PhotoApp::Action::"viewPhoto",
resource == PhotoApp::Photo::"vacationPhoto.jpg"
);
permit (
principal == PhotoApp::User::"stacey",
action == PhotoApp::Action::"viewPhoto",
resource
)
when { resource in PhotoApp::Account::"stacey" };
The text was updated successfully, but these errors were encountered: