035f4d095b
Merge pull request #3131 from strongloop/update-issue-template
...
Update ISSUE_TEMPLATE
2017-01-23 11:17:08 -08:00
c6427065be
Update ISSUE_TEMPLATE
...
- Minor formatting edits to reduce scrolling
- Clean up sentence in the last comment
2017-01-23 10:26:50 -08:00
4c9c6236e3
Merge pull request #3074 from ariskemper/fix_user_id
...
Fix User model to handle custom PK name
2017-01-23 09:43:19 +01:00
9a1f86baef
Merge pull request #3126 from joesepi/updatereadme
...
Updating README to show loopback-cli and remove arc mention
2017-01-20 14:21:37 -08:00
746265b393
Updating README - add cli and remove arc
2017-01-20 17:15:01 -05:00
efd8237dc6
Fix User methods to use correct Primary Key
...
Do not use hard-coded "id" property name, call `idName()` to get the
name of the PK property.
2017-01-20 16:24:59 +01:00
a7d93f32b5
Merge pull request #3120 from strongloop/fix/user-reset-password
...
Fix User.resetPassword to call createAccessToken()
2017-01-20 10:58:31 +01:00
e63fea83f7
Fix User.resetPassword to call createAccessToken()
...
This allows User subclasses to override the algorithm used for building
one-time access tokens for password recovery.
2017-01-19 16:27:22 +01:00
a6d511d8b4
Role model: resolves related models by name
...
Resolve models related to the `Role` model by name instead of class.
2017-01-16 15:48:24 +01:00
ff53933085
3.2.1
...
* Preserve current session when invalidating tokens (Miroslav Bajtoš)
* Clean up access-token-invalidation tests (Miroslav Bajtoš)
* Update docs.json (Rand McKinney)
* Simplify issue template (#3083 ) (Simon Ho)
* Warn about injectOptionsFromRemoteContext (Miroslav Bajtoš)
2017-01-16 12:01:47 +01:00
4ffe5fe17f
Merge pull request #3098 from strongloop/preserve-current-access-token
...
Preserve current session when invalidating access tokens
2017-01-16 10:35:39 +01:00
e17cc3d23a
Preserve current session when invalidating tokens
...
Fix User model to preserve the current session (provided via
"options.accessToken") when invalidating access tokens after a change
of email or password property.
2017-01-16 10:08:30 +01:00
24bb15233d
Clean up access-token-invalidation tests
2017-01-16 10:08:30 +01:00
3946462828
Merge pull request #3097 from strongloop/remove-context-api-doc
...
Update docs.json
2017-01-13 14:28:29 +01:00
9fec6e1615
Update docs.json
...
Remove files that are no longer used.
2017-01-12 14:25:38 -08:00
d2e9e7ee77
Simplify issue template ( #3083 )
...
Favour form editing over going down a checklist. Also fix automatic 2
subtasks creation side effect from old issue template.
2017-01-11 17:04:19 -08:00
b86eac5cf6
Merge pull request #3080 from strongloop/feature/warn-on-injectOptionsFromRemoteContext
...
Warn about injectOptionsFromRemoteContext
2017-01-10 15:38:24 +01:00
3e2ac9217f
Warn about injectOptionsFromRemoteContext
...
The option injectOptionsFromRemoteContext was added to LoopBack 2.x only
and is not available in LoopBack 3.x (and newer).
When a model with this option is encountered, we are printing a warning
message now, to let the user know about this change between 2.x and 3.x.
2017-01-09 14:45:23 +01:00
3ed525f753
3.2.0
...
* Upgrade eslint-config to 7.x (Miroslav Bajtoš)
* Allow password reset request for users in realms (Bram Borggreve)
* Fix construction of sharedCtor remoting metadata (Miroslav Bajtoš)
* Add option disabling periodic change rectification (kobaska)
* Fix annotation for persistedModel.count (lschricke)
* Applied as reviewed by @flowersinthesand (박대선)
* Fix false emailVerified on user model update (박대선)
* Contextify DAO and relation methods (Miroslav Bajtoš)
* Implement new http arg mapping optionsFromRequest (Miroslav Bajtoš)
* Emit resetPasswordRequest event with options (Sergey Reus)
2017-01-09 13:00:18 +01:00
4e6f9b978a
Merge pull request #3075 from strongloop/upgrade-eslint
...
Upgrade eslint-config to 7.x
2017-01-06 12:54:58 +01:00
70eecfab70
Upgrade eslint-config to 7.x
2017-01-06 12:12:35 +01:00
12be94e0db
Merge pull request #2998 from fullcube/bb/password-reset-realms-3.x
...
Allow password reset request for users in realms (v3.x)
2017-01-05 12:34:23 -05:00
cddfb9c77d
Allow password reset request for users in realms
2017-01-05 09:47:18 -05:00
298635dad1
Merge pull request #2992 from DA-14/feature/resetPasswordRequest
...
Emit resetPasswordRequest event with options
2017-01-05 15:33:22 +01:00
8a2c01b3d8
Merge pull request #3070 from strongloop/fix/sharedCtor-remoting
...
Fix construction of sharedCtor remoting metadata
2017-01-05 11:37:30 +01:00
f4b167698a
Merge pull request #3053 from yumenohosi/fix/email-verified
...
Fix false emailVerified on user model update
2017-01-05 11:02:54 +01:00
0a6740cc30
Fix construction of sharedCtor remoting metadata
...
Prevent the situation when we are configuring remoting metadata after
strong-remoting has already picked up data from our parent (base) model.
2017-01-05 10:24:04 +01:00
0d1f74e2cd
Merge pull request #3047 from strongloop/forward-port/avoid-change-cleanup
...
Add option disabling periodic change rectification
2017-01-04 16:39:44 +01:00
355e40d750
Merge pull request #3066 from lschricke/patch-1
...
Fix annotation for persistedModel.count
2017-01-04 10:06:06 -05:00
e15a656714
Add option disabling periodic change rectification
...
When `Model.settings.changeCleanupInterval` is set to a negative value,
no periodic cleanup is performed at all.
2017-01-04 15:58:44 +01:00
baa50518cf
Fix annotation for persistedModel.count
2017-01-03 20:09:42 -05:00
697614dd45
Applied as reviewed by @flowersinthesand
2016-12-23 14:47:08 +09:00
d9ae32429b
Fix false emailVerified on user model update
...
Yesterday, the loopback we are using in our system was upgraded
via npm, and since the upgrade, we noticed that every time
the user model updates, the emailVerified column would change to false.
I took a look and realized there might be an error in
https://github.com/strongloop/loopback/commit/eb640d8
The intent of the commit just mention is to make emailVerified false
when the email gets changed, but notice that ctx.data.email is null
on updates, so the condition is always met and emailVerified always
becomes false.
This commit fixes the issue just mentioned.
2016-12-23 14:04:44 +09:00
a21fca6089
Merge pull request #3023 from strongloop/feature/options-from-context-v2
...
Inject remoting context to options arg
2016-12-22 12:01:02 +01:00
60ea3e96bc
Contextify DAO and relation methods
...
Modify remoting metadata of data-access methods in PersistedModel
and relation method in Model and add an "options" argument to "accepts"
list.
2016-12-22 10:26:09 +01:00
4de3aa77e3
Implement new http arg mapping optionsFromRequest
...
Define a new Model method "createOptionsFromRemotingContext" that allows
models to define what "options" should be passed to methods invoked
via strong-remoting (e.g. REST).
Define a new http mapping `http: 'optionsFromRequest'` that invokes
`Model.createOptionsFromRemotingContext` to build the value from
remoting context.
This should provide enough infrastructure for components and
applications to implement their own ways of building the "options"
object.
2016-12-22 10:26:01 +01:00
668a9d0ed6
3.1.1
...
* Update package.json for LB3 release (Simon Ho)
* Invalidate AccessTokens on password change (Miroslav Bajtoš)
* Fix registration of operation hooks in User model (Miroslav Bajtoš)
* Remove "options.template" from Email payload (Miroslav Bajtoš)
* Upgrade eslint config and grunt-eslint to latest (Miroslav Bajtoš)
* Update paid support URL (siddhipai)
* Update paid support URL (Siddhi Pai)
* Remove duplicate warning in issue template (Siddhi Pai)
2016-12-21 16:05:58 +01:00
f71030f8c2
Merge pull request #3044 from strongloop/release/3.x
...
Prepare for 3.x GA
2016-12-21 10:52:06 +01:00
92ab09338e
Update package.json for LB3 release
2016-12-21 00:54:07 -08:00
f27cd2ccfb
Merge pull request #3018 from strongloop/fix/session-expiry2
...
Invalidate AccessTokens on password change
2016-12-12 13:50:15 +01:00
29a17f39d5
Invalidate AccessTokens on password change
...
Invalidate all existing sessions (delete all access tokens)
after user's password was changed.
2016-12-12 13:30:53 +01:00
fa8bca8d6e
Emit resetPasswordRequest event with options
2016-12-09 18:14:32 +02:00
dac1295ad7
Merge pull request #3016 from strongloop/fix/repeated-user-hooks2
...
Fix registration of operation hooks in User model (part 2)
2016-12-09 15:06:02 +01:00
f476613ab1
Fix registration of operation hooks in User model
...
Follow-up for 4edce47
2016-12-09 14:29:30 +01:00
57a053bbf2
Merge pull request #3014 from strongloop/fix/repeated-user-hooks
...
Fix registration of operation hooks in User model
2016-12-09 14:09:12 +01:00
4edce47b24
Fix registration of operation hooks in User model
...
Operation hooks are inherited by subclassed models, therefore they must
be registered outside of `Model.setup()` function.
This commit fixes this problem in the built-in User model.
There are not tests verifying this change, as writing a test would be
too cumbersome and not worth the cost IMO.
2016-12-09 13:16:42 +01:00
63beaa21fe
Merge pull request #3004 from strongloop/fix/email-template-in-transport
...
Remove "options.template" from Email payload
2016-12-07 10:53:04 +01:00
7f2cdc106c
Merge pull request #3002 from strongloop/eslint-es6
...
Upgrade eslint config and grunt-eslint to latest
2016-12-07 10:52:52 +01:00
5016703f21
Remove "options.template" from Email payload
...
Fix User.confirm to exclude "options.template" when sending the
confirmation email. Certain nodemailer transport plugins are rejecting
such requests.
2016-12-06 16:18:19 +01:00
acdfb432d0
Upgrade eslint config and grunt-eslint to latest
...
- disable ES6 because PhantomJS does not support it yet
- fix linter errors reported after the upgrade.
2016-12-06 16:05:13 +01:00
Simon Ho
Miroslav Bajtoš
Rand McKinney
Joe Sepi
Aris Kemper
João Ribeiro
Benjamin Kroeger
Miroslav Bajtoš
David Cheung
Bram Borggreve
kobaska
lschricke
박대선
Simon Ho
Sergey Reus