Send partner form to Pipedrive

Send partner form to Pipedrive

Bumps minimatch to 3.1.2 and updates ancestor dependency serve. These dependencies need to be updated together.

Updates minimatch from 3.0.4 to 3.1.2

Updates serve from 14.0.1 to 14.2.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

Hey there, we've been using table editor for a while and we have an occurring need from the plugin. We want to be able to add links to the table content.

There are possible solutions to this, here are some we thought of.

1. Structured Text syntax

Currently, we are overcoming this issue by using the Markdown syntax but it's very error prone and it's focused on manual parsing.

As in [Duck Duck Go](https://duckduckgo.com) My favorite search engine is Duck Duck Go.

Is there a plan to add link support to the table plugin? If not do you have any suggestions? Cheers

We have a feature request open for this here: https://community.datocms.com/t/html-table-in-structured-text/2477/12

Please upvote that and I'm closing this to avoid duplication, thanks!

Hello, I have been using @datocms/cma-client-browser for some time now with Expo SDK 45, but after updating to the newest 47 version, builds started failing giving the following error: TypeError: undefined is not an object (evaluating 'navigator.userAgent.includes') I'm not sure whether userAgent is even present by default in the React Native Expo environment but somehow it was working previously.

package version: 1.1.22

Would appreciate help 😄

hello @mkidawa I'm closing this as maybe you are not interested anymore. But if you still need help on this, please reopen.

Do you have plans to implement these missing tags into structured text? <sup>, <sub>

We have some text that has a registered trademark ® also I see this would be useful for dates i.e 22<sup>nd</sup>

We can replace it in a renderNodeRule but this isn't a clean solution.

Since the feature is tracked there already I'm closing this to avoid duplication

Thank you @rodrigobarona I've added this to our backlog, it would require a change in our plugin SDK, so we'll consider this for the future!

Bumps webpack from 5.74.0 to 5.76.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps webpack from 5.74.0 to 5.76.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

If I have a .png media asset and I want to serve it as .png, I couldn't find a way to achieve this on the query level without the asset url getting appended by auto="format". We don't want to serve .avif in this particular case but the actual file that was saved to media assets.

file {
  url
}

Resulting path: https://www.datocms-assets.com/path/to/asset.png?auto=format => serves asset.avif

When it should be:

https://www.datocms-assets.com/path/to/asset.png => serves asset.png

Of course, I could force the format but then every other file format would be served incorrectly.

file {
  url(imgixParams: {fm: "png"})
}

We encountered this issue just recently and think it was working correctly before.

I think the correct behavior should be to explicitly assign parameters if wanted or at least offer an escape hatch:

file {
  url(imgixParams: {auto: "format"})
}

Another way of achieving this would be to strip out the appendix or construct the url from ${host}/${path} but I'd like to avoid that if possible.

hey @vanska sorry for having missed this issue, but have you tried passing auto: "" as an ImgixParam?

I'm going to close for now, but please reopen if necessary

Hey @moritzjacobs sorry for the delay here, the issue was not noticed before :(

Unfortunately what you are asking is not possible as the validations can take a while to finish and happen asyncronously in the background.

You would need to run a separate script that fetches all the invalid records and check how many you have, but it's not something that we can add automatically at the end of every migration unfortunately :(

Hi! Since we ran into trouble with this a few times, it would be really cool to see how many records were invalidated by running a migration on the CLI, kind of like this:

Running migration "1668493138_foobar.ts"... done
Successfully run 1 migration scripts

Summary:
- ✨ 12 new records (Post, Category)
- ⚠️ 4 changed records (Post)
- 🚨 5 invalid records (Page)

Thanks for consideration!

Bumps webpack from 5.74.0 to 5.76.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Hi,

I'm trying to download all the images from datoCMS when building so that I have one less dependency on run-time and so that all my assets point to a local file instead of a remote one with a different domain. I have an article model with Media type on datoCMS, and I can see many of its properties in graphql, such as URL, size, etc.

However, when logging the node object using the createResolvers API, I only see the following:

... "image":{"alt":null,"title":null,"custom_data":{},"focal_point":null,"upload_id":"20946318"} ... The ID is correct, but where is the other information?

Code:

  const { createNode } = actions
  const resolvers = {
    DatoCmsArticle: {
      localImage: {
        type: "File",
        resolve: async (source, args, context, info) => {
          return createRemoteFileNode({
            url: source.entityPayload.attributes.image.url,
            createNode,
            createNodeId,
            reporter,
            cache,
            store,
          })
        },
      },
    },
  }
  createResolvers(resolvers)
}

Am I doing something wrong? Cheers.

I think we are going to add support for this natively with this: https://github.com/datocms/gatsby-source-datocms/pull/189

For regular <img />, it's excellent. I'm trying to make the <img /> behave like a background image, but I can't quite get it right.

Are there any tips to get such a setup working?

hey @grantholle very sorry for the delay in answering this, hoping it can still be useful to someone.

Have a look at the layout="fill" option here: https://github.com/datocms/vue-datocms/tree/master/src/components/Image#layout-mode, it might help your use case?

Hi there,

I need for a project to get the base64 code of an image I upload on DatoCMS. In the Graphql schema base64 is only for blurred image placeholder.

I tried using a resolver to access to the image url and convert it in javascript with no luck as the url field doesn't seem to be accessible by the source arg in my resolve function.

Would you have any lead I could follow to perform this at build time instead of retrieving the url as usual and convert directly inside my page ?

Thanks in advance !