More granular control over editable state about creditcardview

[vinaygaba]

This sounds like an interesting idea. One that I would like to give the users of this library. So would you like to see more attribute fields like app:IsCardNameEditable,app:IsExpiryDateEditable ....... Or do you have any other suggestions of implementing this?

[biddster]

That's just perfect, exactly what I'd like to see.

[vinaygaba]

Great. I think I can do this :)

[vinaygaba]

@VenomVendor I wanted your opinion about this.
Does it make sense to deprecate the isEditable attribute and replace it with 3 different attributes(isCreditCardEditable,isCard........) to give more granular control or should I keep the isEditable attribute as is and along with that add 3 new attributes?

[VenomVendor]

@vinaygaba It's good to have both. I was planning to take this, but you should have already started.

[vinaygaba]

@VenomVendor Yup I started working on this. Was thinking about what the precedence logic should be like.

[vinaygaba]

@biddster I have added support for more granular control of fields. Will be releasing the new version of the library today and updating the documentation accordingly. Closing the issue :)

[vinaygaba]

@biddster This feature is implemented as part of v1.0.3 and I want you to try it out. I have not updated the documentation yet as I am trying to include the flip animation feature as part of the 1.0.3 release. But v1.0.3 is available on maven for you to use as of now and you can try it out. There are 3 additional attributes now: isCardNumberEditable,isCardNameEditable and isExpiryDateEditable.

isEditable field is still available but the granular attributes will have precedence over this field for the respective fields. Do try it out and do let me know what u think.