-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Chore and bugfix/fix thumbnail upload and update dependency versions #123
Chore and bugfix/fix thumbnail upload and update dependency versions #123
Conversation
This is a folder generated during build process of older version if this project. Currently, we don't build this project in any way and generally, build artifacts are not commited on git
…mage upload input
…version and fix breaking changes in code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might lead to a breaking change for those people who have cloned the repo and made some changes in the previous puppeteer version. To me it's okay to just go for it, we should underline the change in the next release's changelog
@TheJoin95 Could you elaborate please? IF someone cloned the repo before this PR, then, normally, people sync their repos with latest changes from master before making changes in the code, right? |
async function clickXpath(page, xpath, options = {}) { | ||
await page.waitForXPath(xpath, options); | ||
const [elementHandle] = await page.$x(xpath); | ||
await clickDom(page, elementHandle); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry to have not been clear: I was referring to this function being removed.
So people who used the function previously, they won't be able to do it anymore.
Anyway, I'm ok to drop the use of this function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, you are right, but normally, if someone wants to make a PR, or sync with latest changes from our master, they would need to apply the change in their code that they maintain for themselves. Good to note in release notes anyway, it would benefit the maintainers of private forks for example.
Here I list the coomits made by this PR to better understand what was done:
This is a folder generated during build process of older version if this project. Currently, we don't build this project in any way and generally, build artifacts are not commited on git