Skip to content

public attribute handling in multi-config scenario #105

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.

Sign up for GitHub

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

Jump to bottom
Open
Qwaz opened this issue Feb 2, 2019 · 0 comments
Open

public attribute handling in multi-config scenario #105

Qwaz opened this issue Feb 2, 2019 · 0 comments
Labels
deferred Will be handled later enhancement Improvements on performance or other factors

Comments

@Qwaz
Copy link
Member

Qwaz commented Feb 2, 2019 •
edited
Loading

If the value of public attribute is different among configurations, we are going to use any with exceptional rejection strategy.

As public attribute has a default value of "false", setting public on any "true" value looks natural.
However, if Soma detects explicit settings of both (i.e. explicit "true" and "false") we should reject it as it is apparently a bad configuration.
@Qwaz Qwaz added deferred Will be handled later enhancement Improvements on performance or other factors labels Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deferred Will be handled later enhancement Improvements on performance or other factors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Qwaz