Skip to content
New issue

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

[Feature Request] Implement Cedar policy language by default #4717

Open
2 tasks done
parthdedaniya opened this issue Oct 17, 2024 · 0 comments
Open
2 tasks done

[Feature Request] Implement Cedar policy language by default #4717

parthdedaniya opened this issue Oct 17, 2024 · 0 comments
Labels
feature-request Request for new features or functionality

Comments

@parthdedaniya
Copy link

Context

  • 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.

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" };

@parthdedaniya parthdedaniya added the feature-request Request for new features or functionality label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

1 participant