Skip to content
This repository was archived by the owner on Dec 20, 2023. It is now read-only.

Conversation

@StevenWatremez
Copy link
Contributor

@StevenWatremez StevenWatremez commented Mar 15, 2018

Drop support for realmReadOnly user info key - fixes #28

enum Attributes: String {
{%- for attribute in entity.attributes -%}
{%- if attribute.realm_ignored or attribute.realm_read_only.size == 0 -%}
{%- if attribute.realm_ignored == false -%}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 how come did it work before that == false?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how it worked before I remove realmReadOnly, it was a bug. But with unit tests I saw that attribute.realm_ignored is not a valid statement. So I copy existing comparison and now it works with attribute.realm_ignored == false

@AliSoftware
Copy link
Collaborator

⚠️ This will need us to do a major version, as the generated code will be a breaking change for apps using it

@AliSoftware AliSoftware force-pushed the feature/remove-realm-read-only branch from 07e6c44 to cc40243 Compare March 23, 2018 10:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stop handling realmReadOnly

3 participants