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

Conventions for error reason string #227

Closed
jclark opened this issue Jun 18, 2019 · 2 comments
Closed

Conventions for error reason string #227

jclark opened this issue Jun 18, 2019 · 2 comments
Assignees
Labels
lang Relates to the Ballerina language specification langlib Relates to lang.* libraries platform Relates to the Ballerina platform status/pending Design is agreed and waiting to be added
Milestone

Comments

@jclark
Copy link
Collaborator

jclark commented Jun 18, 2019

We need to decide on some conventions for the format of strings used for error reasons. This affects

@jclark jclark added lang Relates to the Ballerina language specification status/discuss Needs discussion outside github comments platform Relates to the Ballerina platform langlib Relates to lang.* libraries labels Jun 18, 2019
@jclark jclark added this to the 2019R2 milestone Jun 18, 2019
@jclark
Copy link
Collaborator Author

jclark commented Jun 20, 2019

Current idea is to use format {org/module}CamelCase.

@jclark
Copy link
Collaborator Author

jclark commented Jun 20, 2019

Language defined errors will have the format {ballerina/lang.*}CamelCase.

@jclark jclark added status/pending Design is agreed and waiting to be added and removed status/discuss Needs discussion outside github comments labels Jun 20, 2019
@jclark jclark closed this as completed in 8b5a06a Jun 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lang Relates to the Ballerina language specification langlib Relates to lang.* libraries platform Relates to the Ballerina platform status/pending Design is agreed and waiting to be added
Projects
None yet
Development

No branches or pull requests

2 participants