Collections of packages and tools for working with Go programming language. http://git.kilabit.info/pakakeh.go/atom?h=v0.57.0 2024-09-03T18:09:51Z 2024-09-03T18:09:51Z Shulhan ms@kilabit.info 2024-09-02T17:16:13Z urn:sha1:061cf9bf6072e0f718c6c16935caf218d05da5de === Breaking changes * lib/sql: replace [http.FileSystem] with [memfs.MemFS] Accepting the [http.FileSystem] means that the parameter can receive an instance of [embed.FS], but in most cases, it will fail. Case example, when we embed SQL files for migration under "db/migration" using the "go:embed" directive, //go:embed db/migration/*.sql var DBMigrationFS embed.FS and then call the [Migrate] function, it will not find any ".sql" files inside the "/" directory because the files is stored under "db/migration/" prefix (also there is no "/" when using embed.FS). === Chores * lib/memfs: document the comparison with "go:embed" directive Compare it to "go:embed", the memfs package is more flexible and portable. Currently, we found three disadvantages of using "go:embed", - The "go:embed" only works if files or directory to be embedded is in the same parent directory. - Accessing the embedded file require the original path. - No development mode. None of those limitation affected the memfs package. 2024-09-03T18:09:51Z Shulhan ms@kilabit.info 2024-09-02T17:36:12Z urn:sha1:bea911e27eb064653e46493320d3a15061672acc While at it, temporary disable gosec due to excessive report for G115, which may be true, but may also break the current working program. We should alter and fix once we can test and make sure that it does not breaks. 2024-09-02T17:16:00Z Shulhan ms@kilabit.info 2024-09-02T17:16:00Z urn:sha1:218aad17a7f92169b1bd75fccb8a3c87cde0cf8b 2024-08-09T09:34:57Z Shulhan ms@kilabit.info 2024-08-09T09:34:57Z urn:sha1:437d1090ef8b94b8de784eb27f2cf85bcfc1fc6e Accepting the [http.FileSystem] means that the parameter can receive an instance of [embed.FS], but in most cases, it will fail. Case example, when we embed SQL files for migration under "db/migration" using the "go:embed" directive, //go:embed db/migration/*.sql var DBMigrationFS embed.FS and then call the [Migrate] function, it will not found any ".sql" files inside the "/" directory because the files is stored under "db/migration/" prefix (also there is no "/" when using embed.FS). 2024-08-09T08:21:01Z Shulhan ms@kilabit.info 2024-08-09T08:21:01Z urn:sha1:473738cfc9b33c18ee749112c7d248f4f626e7fb Compared it with "go:embed", the memfs package is more flexible and portable. Currently, we found three disadvantages of using "go:embed", #1 - The "go:embed" only works if files or directory to be embedded is in the same parent directory. #2 - Accessing the embedded file require the original path. #3 - No development mode. 2024-08-04T04:33:49Z Shulhan ms@kilabit.info 2024-08-04T04:29:59Z urn:sha1:f703cf50a4e3b2092a5ad615eef9bd56f58a25d3 == New features * cmd/emaildecode: CLI to decode email body to plain text The emaildecode accept file as input. If the email header contains content-transfer-encoding with value quoted-printable or base64, it will decode the message body and print it to stdout as plain text. == Bug fixes * lib/memfs: another fix for refresh In previous commit we use wrong condition when handling directory "." as Root. == Enhancements * lib/email: allow message that end lines with LF only Although, a message from network must end with CRLF, a message from (another) client may have been sanitized and end with LF only. * lib/email: decode the message body based on content-transfer-encoding After the header and body has been parsed, if the header contains Content-Transfer-Encoding, we decode the body into its local formats. Currently supported encoding is "quoted-printable" and "base64". == Others * lib/email: export the Header fields By exporting the fields, this allow the caller to filter or manage the field manually. * _doc: add partial note and summary for RFC 2183 The RFC 2183 is define Content-Disposition header field in the internet message. * lib/ini: mention that marshaling []byte does not supported Due to "byte" is considered as "uint8" during reflection, we cannot tell whether the value is slice of byte of slice of number with type uint8. 2024-08-04T04:33:49Z Shulhan ms@kilabit.info 2024-08-03T11:00:40Z urn:sha1:b70c8ab9bc3225a5cbad746902e4252477500e7b Due to "byte" is considered as "uint8" during reflection, we cannot tell whether the value is slice of byte of slice of number with type uint8. 2024-08-04T04:33:49Z Shulhan ms@kilabit.info 2023-09-19T18:07:59Z urn:sha1:426f3df9aaf6d4788567da2f7ca17ce14cb56b38 The RFC 2183 is define Content-Disposition header field in the internet message. 2024-08-04T04:33:49Z Shulhan ms@kilabit.info 2024-01-24T17:20:53Z urn:sha1:4ae360c5adc25051136ce638f85c7c10f856d9d3 The emaildecode accept file as input. If the email header contains content-transfer-encoding with value quoted-printable or base64, it will decode the message body and print it to stdout as plain text. 2024-08-04T04:33:27Z Shulhan ms@kilabit.info 2024-08-03T04:50:24Z urn:sha1:9902b65d3feef74a30001b8f150299467693e699 By exporting the field, this allow the caller to filter or manage the Header Fields manually.