Skip to content

Releases: Permify/permify-node

v1.0.9

30 Oct 14:13
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.0.8...v1.0.9

v1.0.8

28 Oct 06:35
Compare
Choose a tag to compare
Update generated sdk directory with latest changes

v1.0.7

27 Sep 20:39
Compare
Choose a tag to compare
  • new parameters added for tls enabled connections:

pk -> primary key
certChain -> certificate chain

v1.0.5

25 Sep 11:49
Compare
Choose a tag to compare
  • fix: rebuilt

v1.0.4

19 Sep 15:42
Compare
Choose a tag to compare

Release Notes

After receiving feedback from the community, we have reverted the parameter structure of our client functions to match the structure from v0.4.6 and earlier versions.

With this release, defining a schema will be as follows:

client.schema.write({
    tenantId: "t1",
    schema: `
    entity user {}
    
    entity document {
       relation viewer @user
       
       action view = viewer
    }
    `
});

What's Changed

  • fix: no cert connections are fixed by @ucatbas in #93

Full Changelog: v0.4.9...v1.0.4

v0.4.9

05 Aug 13:17
Compare
Choose a tag to compare

Release Notes

  • SDK Generation: SDKs are now generated using the official buf gRPC Node generator.

  • Unified Data Access: All data is accessable through the grpc.payload, grpc.base, or simply grpc properties.

  • Configuration Update: This version requires updating your configuration to include the buf registry in your npm settings. Make sure to add the necessary entries to your npm configuration to leverage the new SDKs.

  • Object-Based Data Handling: Dictionary-typed data bodies are transitioned from sending to requiring objects to be created and set.

In versions earlier than v0.4.6, writing a schema could be done using the client.schema.write function with a dictionary option:

client.schema.write({
    tenantId: "t1",
    schema: `
    entity user {}
    
    entity document {
       relation viewer @user
       
       action view = viewer
    }
    `
});

With this release, writing a schema now involves creating and setting the appropriate request objects:

let schema = `
    entity user {}
    
    entity document {
       relation viewer @user
       
       action view = viewer
    }
`;
let schemaWriteRequest = new permify.grpc.payload.SchemaWriteRequest();
schemaWriteRequest.setTenantId("t1");
schemaWriteRequest.setSchema(schema);

client.schema.write(schemaWriteRequest);

This pattern will be applied to all similar functions, where dictionary-typed data bodies are transitioned to requiring objects to be created and set. Please make sure to migrate your code accordingly.

v0.4.6

24 Feb 17:30
Compare
Choose a tag to compare
feat: v0.7.6 updates

v0.4.5

01 Dec 08:58
Compare
Choose a tag to compare
*: package json version update

v0.4.4

01 Dec 08:57
Compare
Choose a tag to compare
feat: v0.6.1 updates

v0.4.3

02 Nov 07:33
Compare
Choose a tag to compare
feat: v0.5.6 updates