Skip to content

Perhaps we can now unexpose removeAttr from the API?#100

Open
aawwawa wants to merge 1 commit into
ded:masterfrom
aawwawa:patch-1
Open

Perhaps we can now unexpose removeAttr from the API?#100
aawwawa wants to merge 1 commit into
ded:masterfrom
aawwawa:patch-1

Conversation

@aawwawa

@aawwawa aawwawa commented Nov 26, 2012

Copy link
Copy Markdown
Contributor

Clean APIs are nice, right?

@aawwawa

aawwawa commented Nov 26, 2012

Copy link
Copy Markdown
Contributor Author

Make for lighter docs, too...

@rvagg

rvagg commented Oct 14, 2013

Copy link
Copy Markdown
Collaborator

I'm fine with this too as long as we can have some tests (sorry for the 11 month delay on commenting!)

@ryanve

ryanve commented Oct 14, 2013

Copy link
Copy Markdown
Contributor

removeAttr() should stay exposed for jQuery compatibility.

@rvagg

rvagg commented Oct 14, 2013

Copy link
Copy Markdown
Collaborator

good call @ryanve, I didn't know that was a jQuery thing.

@ded

ded commented Oct 15, 2013

Copy link
Copy Markdown
Owner

strange. so what needs to change or not change?

@ded

ded commented Oct 15, 2013

Copy link
Copy Markdown
Owner

i see. yes. if we keep it, then that is correct, we should just make it check for null

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.

4 participants