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

Update dependency @pankod/refine-react-router-v6 to v3.40.0 #2397

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pankod/refine-react-router-v6 (source) 3.22.1 -> 3.40.0 age adoption passing confidence

Release Notes

refinedev/refine (@​pankod/refine-react-router-v6)

v3.40.0

Compare Source

Minor Changes

v3.39.0

Compare Source

Minor Changes

v3.38.0

Compare Source

Minor Changes

v3.37.0

Compare Source

Minor Changes

v3.36.6

Compare Source

Patch Changes

v3.36.5

Compare Source

Patch Changes

v3.36.4

Compare Source

Patch Changes

v3.36.3

Compare Source

Patch Changes

v3.36.2

Compare Source

Patch Changes
  • Add missing BrowserRouterComponent export to @pankod/refine-react-router-v6 package.

v3.36.1

Compare Source

Patch Changes

v3.36.0

Compare Source

Minor Changes
  • Added ability to manage the initial route of refine by binding initialRoute variable to RouterComponent component.

v3.35.0

Compare Source

Minor Changes
  • Added ability to manage the initial route of refine by binding initialRoute variable to RouterComponent component.

v3.34.0

Compare Source

Minor Changes
  • #​2486 ee4d0d112a Thanks @​aliemir! - Added ability to manage the initial route of refine by binding initialRoute variable to RouterComponent component.

v3.33.2

Compare Source

Patch Changes
  • Fixed version of react-router to 6.3.0

v3.33.1

Compare Source

Patch Changes

v3.33.0

Compare Source

Minor Changes
  • Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

v3.32.0

Compare Source

Minor Changes
  • #​2440 0150dcd070 Thanks @​aliemir! - Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

v3.31.3

Compare Source

Patch Changes
  • Fixed default login page is <LoginPage>.
  • 🎉 Added AuthPage component to the refine app. This page is used to login, register, forgot password and update password. Login page is default page and old LoginPage component is deprecated.

v3.31.2

Compare Source

Patch Changes

v3.31.1

Compare Source

Patch Changes
  • #​2299 a02cb9e8ef Thanks @​biskuvit! - 🎉 Added AuthPage to the refine app. This page is used to login, register, forgot password and update password. Login page is default page and old LoginPage component is deprecated.

v3.31.0

Compare Source

Minor Changes
  • Add React@18 support 🚀

v3.30.0

Compare Source

Minor Changes

v3.29.0

Compare Source

Minor Changes
  • Pass the full resource to the accessControlProvider can method. This will enable Attribute Based Access Control (ABAC), for example granting permissions based on the value of a field in the resource object.

    const App: React.FC = () => {
      <Refine
        // other providers and props
        accessControlProvider={{
          can: async ({ resource, action, params }) => {
            if (resource === "posts" && action === "edit") {
              return Promise.resolve({
                can: false,
                reason: "Unauthorized",
              });
            }
    
            // or you can access directly *resource object
            // const resourceName = params?.resource?.name;
            // const anyUsefulOption = params?.resource?.options?.yourUsefulOption;
            // if (resourceName === "posts" && anyUsefulOption === true && action === "edit") {
            //     return Promise.resolve({
            //         can: false,
            //         reason: "Unauthorized",
            //     });
            // }
    
            return Promise.resolve({ can: true });
          },
        }}
      />;
    };

v3.28.0

Compare Source

Minor Changes
  • e78b181b12 Thanks @​omeraplak! - Pass the full resource to the accessControlProvider can method. This will enable Attribute Based Access Control (ABAC), for example granting permissions based on the value of a field in the resource object.

    const App: React.FC = () => {
      <Refine
        // other providers and props
        accessControlProvider={{
          can: async ({ resource, action, params }) => {
            if (resource === "posts" && action === "edit") {
              return Promise.resolve({
                can: false,
                reason: "Unauthorized",
              });
            }
    
            // or you can access directly *resource object
            // const resourceName = params?.resource?.name;
            // const anyUsefulOption = params?.resource?.options?.yourUsefulOption;
            // if (resourceName === "posts" && anyUsefulOption === true && action === "edit") {
            //     return Promise.resolve({
            //         can: false,
            //         reason: "Unauthorized",
            //     });
            // }
    
            return Promise.resolve({ can: true });
          },
        }}
      />;
    };

v3.27.0

Compare Source

Minor Changes
  • All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #​2183. (having more than one @​pankod/refine-core version in node_modules and creating different instances)

    Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

Patch Changes
  • Fix adding the current path to the to parameter when redirecting to the login page after logout - #​2211

v3.26.0

Compare Source

Minor Changes
  • #​2217 b4aae00f77 Thanks @​omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #​2183. (having more than one @​pankod/refine-core version in node_modules and creating different instances)

    Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

v3.25.3

Compare Source

Patch Changes

v3.25.2

Compare Source

Patch Changes
  • Fixed a bug that caused <ErrorComponent/> to does not appear in the 404 state

v3.25.1

Compare Source

Patch Changes

v3.25.0

Compare Source

What's Changed

v3.22.2

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot merged commit 61e2463 into main Sep 18, 2024
7 checks passed
@renovate renovate bot deleted the renovate/pankod-refine-react-router-v6-3.x branch September 18, 2024 19:44
@odlbot odlbot mentioned this pull request Sep 19, 2024
4 tasks
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.

0 participants