apache / apache/fesod

[Task] Implement more commonly used converter classes

Open
#1,017 20 comments 0 reactions 0 assignees View on GitHub
discussion welcome good first issue help wanted
Dominant language
Java
Stars
6.2k
Forks
532
Avg merge
1d 3h
Merged PRs (30d)
42

Description

### Motivation

During usage, we may need to convert read or written data into specific formats. Apache Fesod (Incubating) provides a flexible converter mechanism that allows users to define custom data conversion rules to meet various business requirements. Many converter classes are already built in, but some are still missing.

### How to complete

Please link this issue in the description of the PR.

This will be a long-term task, allowing all the volunteers to divide it into multiple PRs for completion. Each PR can contain one or more converters, and each converter needs to provide the corresponding unit test code.

Only classes compatible with **JDK 8** are supported. Each converter must implement the `org.apache.fesod.sheet.converters.Converter` interface, and please leave a comment outlining your specific implementation proposal.

### Task List

The following are some conversions that are currently required
- [ ] `java.sql.Timestamp` @SyedIshmumAhnaf
- [ ] `java.sql.Clob` @AhmedYoussef98
- [ ] `java.time.ZonedDateTime` @alexsmolya
- [x] `java.time.LocalTime` @leehaut
- [ ] `java.time.OffsetDateTime` @Mikkey-f

Please feel free to suggest any type converters you require, and please leave a comment in this issue.

**The new proposal needs to be published for at least 24 hours. If there are no objections during this period, please feel free to submit your PR at any time. These will be added to the task list and assigned to volunteers later.**

Contributor guide

Open the contributing guide

Research direction

Start by locating existing implementations of the org.apache.fesod.sheet.converters.Converter interface and their unit tests. Choose an unclaimed converter from the task list, implement it with JDK 8 compatibility, add its corresponding unit tests, and leave the required implementation proposal comment on the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.