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

fix getting a setting #3

Merged
merged 2 commits into from Jun 12, 2020
Merged

fix getting a setting #3

merged 2 commits into from Jun 12, 2020

Conversation

manuelvilche
Copy link
Member

Joaco, te hago el PR con el fix del clientSetting.get() por si alguien quiere arrancar a usarlo, que funcione! y luego mejoramos lo de la case estatica!

limit: 1,
unique: true
});
sinon.assert.calledTwice(ClientSettingsModel.prototype.getBy);
Copy link
Member

Choose a reason for hiding this comment

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

Ojo aca.. SI ya getteó las settings de una entidad de la DB, no debería ir de nuevo.. Esto estaba así pensando en que se guardaba un registro por entidad+setting, pero ahora que se guarda uno por entidad no debería ir de nuevo a la base por la misma entidad!

Copy link
Member Author

Choose a reason for hiding this comment

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

corregido! ahora hace siempre 1 get, ya sea que busques una o mas settings, cachea todo

@jormaechea jormaechea merged commit b9c48aa into master Jun 12, 2020
@jormaechea jormaechea deleted the fix-client-settings-get branch June 12, 2020 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants