Skip to content

Commit 3da5a7f

Browse files
test cleanup
1 parent 6c93b9c commit 3da5a7f

File tree

2 files changed

+1
-31
lines changed

2 files changed

+1
-31
lines changed

TestWasm/Models/Person.cs

-2
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,6 @@ public class Person
2727

2828
[MagicUniqueIndex("guid")]
2929
public Guid GUIY { get; set; } = Guid.NewGuid();
30-
31-
[MagicEncrypt]
3230
public string Secret { get; set; }
3331

3432
[MagicNotMapped]

TestWasm/Program.cs

+1-29
Original file line numberDiff line numberDiff line change
@@ -24,35 +24,7 @@
2424
{
2525
options.Name = DbNames.Client;
2626
options.Version = 1;
27-
options.EncryptionKey = EncryptionKey;
28-
options.StoreSchemas = SchemaHelper.GetAllSchemas(DbNames.Client);
29-
options.DbMigrations = new List<DbMigration>
30-
{
31-
/*
32-
* The DbMigration is not currently working or setup!
33-
* This is an example and idea I'm thinking about, but
34-
* this will very likely be depreciated so do not use or rely
35-
* on any of this syntax right now. If you want to have
36-
* your own migration knowledge. Write JavaScript on the front end
37-
* that will check the indedDb version and then apply migration code
38-
* on the front end if needed. But this is only needed for complex
39-
* migration projects.
40-
*/
41-
new DbMigration
42-
{
43-
FromVersion = "1.1",
44-
ToVersion = "2.2",
45-
Instructions = new List<DbMigrationInstruction>
46-
{
47-
new DbMigrationInstruction
48-
{
49-
Action = "renameStore",
50-
StoreName = "oldStore",
51-
Details = "newStore"
52-
}
53-
}
54-
}
55-
};
27+
options.StoreSchemas = SchemaHelper.GetAllSchemas(DbNames.Client);
5628
});
5729

5830
await builder.Build().RunAsync();

0 commit comments

Comments
 (0)