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

Add named export for getDomElements #433

Merged
merged 2 commits into from
Oct 26, 2024

Conversation

Doltario
Copy link

So that the method is accessible from the outside, at least useful to fully customize ConnectionWrapper.

Also, kept it as default to not break anything.

It completes work done in #408.

Really tiny PR but I felt bad only commenting issues. Also it made me pretty sure I don't mess with anything ^^
If you want to do it your way, feel free to take or rework that change !

PS: I prepared changes to delete default export inside domResolver, to have only named exports. If you think it would be better, let me know so that I can push it.

So that it is accessible from the outside, at least useful to fully customize ConnectionWrapper.

Also, kept it as default to not break anything.
@newcat
Copy link
Owner

newcat commented Oct 23, 2024

Thank you! Feel free to push the change with named exports; I usually only use named exports that's also why I didn't check it when I added the export in the index.ts file.

…lver

Also, updated imports to remove default import usage.
@Doltario
Copy link
Author

Hey, it is pushed !

I ran yarn test and tried temporary connection through yarn playground. Everything seems fine, I don't know if there is more to do in the process.

Copy link
Owner

@newcat newcat left a comment

Choose a reason for hiding this comment

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

Perfect, thank you!

@newcat newcat merged commit 96ff993 into newcat:master Oct 26, 2024
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.

3 participants