The module works great, however can there be a feature to name the tokens. This really helps us in tracking to whom we have shared the token with and what token to expire / delete in case required.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 3144610-12.patch | 6.61 KB | shaktik |
| #10 | 3144610-10.patch | 6.65 KB | shaktik |
| #8 | 3144610-8.patch | 5.25 KB | shaktik |
| #5 | 3144610-5.patch | 4.19 KB | shaktik |
| #2 | 3144610-2.patch | 8.16 KB | shaktik |
Issue fork access_unpublished-3144610
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
shaktikComment #3
shaktikHi @Vaibhav,
Created patch kindly check.
Thanks,
Shakti.
Comment #5
shaktikTesting to the Removed Test case.
Comment #6
shaktikComment #8
shaktikupdate patch #5 forgot to add AccessToken.php file for the added new title field. and working on install file for an existing installed module use case (need to create install file to Updating Database Schema/Data).
Comment #9
shaktikComment #10
shaktikAdded install file to Update Database Schema/Data for an existing module, Kindly check.
Comment #11
sharma.amitt16 commented@shakti thanks for the patch. Please find my small suggestions here
break the parameters in separate line to keep the line length to 80 characters.
We can merge these two changes in single hook_update.
Description is little bit confusing.
Would you please modify this to
Default value of token name is 'None'.
Comment #12
shaktikThanks, @sharma.amitt16,
I have updated above point, kindly check.
Comment #13
shaktikComment #14
generalredneckComment #17
mably commentedComment #18
mably commentedMR created with some tests.
Wondering if we should add a config option to enable/disable this feature.
So people who don't need it won't be bothered with the extra fields/infos.
Comment #19
generalredneckLooking at this feature. I like what I see so far. The configured default of "None" is a little wierd to me but I can't come up with better suggestions other than leaving it un-named all together. That label is going to be subjective. I can see where people are going to want to add token support to that in the future... that's for another day.
The other thing is... the default is "None" but the upgrade does nothing to label all the tokens prior to the upgrade. They will effectively have NULL as that field value and I'm not sure if that won't bite someone in the butt later. Thoughts?
I really like where this is going though.
Comment #20
mably commented"None" was in the original patch, I would rather go with an empty string too.
I can change the hook to process all existing tokens.
Comment #21
mably commentedSuggestions have been implemented.
Comment #22
generalredneckThis works excellently in my manual testing. It's going into 1.x-dev